Re: [Server-devel] XSCE Proposal | Moving to github and notifications
Thx for the reply! On Tue, Oct 8, 2013 at 7:38 PM, Martin Dluhos mar...@gnu.org wrote: On 10/08/2013 03:08 PM, Anish Mangal wrote: Hi, One of the topics brought up in today's meeting was making the code and development process more visible. Can we have a discussion on this list and come to a conclusion on the proposals listed below. Thanks for sending the summary. I am including my thoughts inline. Proposal-1 : Shifting from redmine to github Pros: * Github offers a much better collaborative workflow with pull requests. * Github offers better code visibility and reviews in the GUI itself. This is a good move for both of the reasons you have listed above. This will lend more credibility to the project attracting the attention of more developers. Also make sure to add a link to the github page on schoolserver.org, so that it is immediately obvious where to access and browse the existing codebase. Proposal-2 : Notifications for source code commits to IRC. This is a well accepted practice to keep community members informed and involved about code changes and the development process. 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. +1 to notifications related to pull requests rather than individual commits. Proposal-3 : Notifications for source code commits to the mailing list. This is a deliberate effort to again encourage better transparency, collaboration. Option-A : Send the notifications to server-devel. Since the mailing list is the single static archived place where everyone is subscribed, it makes sense to send notifications here. Option-B : Send to a separate mailing list. Those who are interested in development, may subscribe to it. Option-C : Github already offers the functionality to subscribe to updates. Individual users can sign up to get notified about updates to the repository. I vote for option C as there is no need to reinvent the wheel for existing functionality Github already offers. servel-devel should serve only for dev discussions, imho. Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XSCE Proposal | Moving to github and notifications
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@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] XSCE Proposal | Moving to github and notifications
Hi, One of the topics brought up in today's meeting was making the code and development process more visible. Can we have a discussion on this list and come to a conclusion on the proposals listed below. Proposal-1 : Shifting from redmine to github * Move the xsce source code from the repository hosted on redmine to a repository hosted on github. * For open/public repositories, github offers an unlimited amount of members and collaboration. This comes at a zero dollar cost. * A xsce user will be created and the xsce repository hosted under it. All people who have commit access currently will have the same rights. * The buildbot will be pointed to the github repo, so builds will continue as usual. * Eg: DXS is on github, Sugar has been on github for quite a while. From the experience of DXS team (Me, Santi, Anna, Miguel), this is a recommended step. Pros: * Github offers a much better collaborative workflow with pull requests. * Github offers better code visibility and reviews in the GUI itself. * Here's an explanatory video that Miguel created: http://www.youtube.com/watch?v=CEE85F3Zjcs Proposal-2 : Notifications for source code commits to IRC. This is a well accepted practice to keep community members informed and involved about code changes and the development process. Proposal-3 : Notifications for source code commits to the mailing list. This is a deliberate effort to again encourage better transparency, collaboration. Option-A : Send the notifications to server-devel. Since the mailing list is the single static archived place where everyone is subscribed, it makes sense to send notifications here. Option-B : Send to a separate mailing list. Those who are interested in development, may subscribe to it. Option-C : Github already offers the functionality to subscribe to updates. Individual users can sign up to get notified about updates to the repository. Thoughts, Anish ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel