[Server-devel] [XSCE] Re: XSCE Proposal | Moving to github and notifications

[George Hunt]

I like github, based upon my limited experience, because of its
browsability. There will be new workflows that need to be established, but
I'm willing for it.

My sense of it is that this becoming a activitycentral project, which is ok
with me. I'm glad when people start putting a shoulder to the wheel.

We need to start  adding value in the classroom as soon as possible, and
github is an intermediate objective, but a distraction, from that objective.

+1 for github

george


On Sun, Oct 13, 2013 at 2:11 PM, Anish Mangal <anish at activitycentral.com>wrote:

> *If* there is consensus on moving to github, should be think about making
> the switch before the hacksprint in SF? It might save us some time as then
> we would have set-up the buildbot, etc.
>
> On the other hand, if there isn't consensus, maybe the hacksprint would be
> a good opportunity to try github out.
>
>
> On Wed, Oct 9, 2013 at 8:30 AM, Martin Dluhos <martin at gnu.org> wrote:
>
>> On 10/09/2013 11:13 AM, Anish Mangal wrote:
>> >> I think that it would be more appropriate to send notifications of
>> merged pull
>> >> > requests rather than individual commits to avoid too much noise on
>> the channel.
>> >> > Those who are interested can always follow the pull request link to
>> access
>> >> > individual commits.
>> >> >
>> > I would prefer notifications for pull requests *both* when they are
>> > created and when they are merged. The creation of the pull request
>> > will sort of open a review and test window for people willing to do
>> > that, so notifying that event is necessary IMO.
>>
>> Very good point. I agree.
>> _______________________________________________
>> Server-devel mailing list
>> Server-devel at lists.laptop.org
>> http://lists.laptop.org/listinfo/server-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/server-devel/attachments/20131013/1931ec61/attachment-0001.html>