Hi,
this year in a Gsoc project, following a proposal by the student, we are using a dedicated mailing list for his project. I think it is a great solution because: - interested people can follow the project without bothering usual mailing lists - the evolution of the project is recorded and public for future reference - offers more flexibility than plain email, because each participant can decide how many messages to get
OTOH, by using a Googlegroup we are outside of the typical development channels, creating an artificial island. I was wondering if Phabricator offer a solution for this? Or is there a way to connect a mailing list to a bug report? I'm thinking of ad-hoc mailing lists like documents in etherpad.
Micru
We are going to discuss Google Summer of Code and FOSS Outreach Program for Women in 90 minutes at #wikimedia-office -- join us!
https://www.mediawiki.org/wiki/Engineering_Community_Team/Meetings/2014-05-2... On Tuesday, May 20, 2014, David Cuenca dacuetu@gmail.com wrote:
this year in a Gsoc project, following a proposal by the student, we are using a dedicated mailing list for his project.
I understand why you are deciding to create a mailing list, but at the same time I'm hoping that in the very near future situations like these can be solved with Phabricator, the tool that is planned to deprecate Bugzilla, Gerrit and several tools more.
https://www.mediawiki.org/wiki/Phabricator
In fact, instead of creating a mailing list that will be surely ignored and forgotten by the rest of the community, I encourage you to run your short-term project with a clear deadline at http://fab.wmflabs.org/
In a Phabricator project all the discussions can be organized around tasks. You can have a generic "Planning Project X" for the meta-discussion. This will give you a space for discussion integrated with project planning and code review.
Phabricator allows you to assign tasks to more than one project, which means that in our production instance you will be able to mark tasks as bugs in other MediaWiki components. Another interesting feature is the possibility for users to subscribe to keywords. This means that having a task related to "Python" might bring the attention of other Python developers, even if they had no prior idea about the existence of your project.
This way of working is a lot more efficient and sustainable than separate mailing lists for projects. I encourage you to give it a try! For what is worth, there is at least one GSoC project using Phabricator.
Chemical Markup for Wikimedia Commons http://fab.wmflabs.org/project/view/26/
Hi Quim
I just posted an email titled "Silly question? Which list is meant for what?". I wonder if you would have the time to weigh in on that on the last point (2.a)) of the email.
Best regards,
Rui
2014-05-20 16:39 GMT+02:00 Quim Gil qgil@wikimedia.org:
We are going to discuss Google Summer of Code and FOSS Outreach Program for Women in 90 minutes at #wikimedia-office -- join us!
https://www.mediawiki.org/wiki/Engineering_Community_Team/Meetings/2014-05-2... On Tuesday, May 20, 2014, David Cuenca dacuetu@gmail.com wrote:
this year in a Gsoc project, following a proposal by the student, we are using a dedicated mailing list for his project.
I understand why you are deciding to create a mailing list, but at the same time I'm hoping that in the very near future situations like these can be solved with Phabricator, the tool that is planned to deprecate Bugzilla, Gerrit and several tools more.
https://www.mediawiki.org/wiki/Phabricator
In fact, instead of creating a mailing list that will be surely ignored and forgotten by the rest of the community, I encourage you to run your short-term project with a clear deadline at http://fab.wmflabs.org/
In a Phabricator project all the discussions can be organized around tasks. You can have a generic "Planning Project X" for the meta-discussion. This will give you a space for discussion integrated with project planning and code review.
Phabricator allows you to assign tasks to more than one project, which means that in our production instance you will be able to mark tasks as bugs in other MediaWiki components. Another interesting feature is the possibility for users to subscribe to keywords. This means that having a task related to "Python" might bring the attention of other Python developers, even if they had no prior idea about the existence of your project.
This way of working is a lot more efficient and sustainable than separate mailing lists for projects. I encourage you to give it a try! For what is worth, there is at least one GSoC project using Phabricator.
Chemical Markup for Wikimedia Commons http://fab.wmflabs.org/project/view/26/
-- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
wikimedia-l@lists.wikimedia.org