Hi Abhishek, On Friday 06 March 2015 12:17 PM, babhishe...@yahoo.co.in wrote: > Hello, > > I am Computer Engineering student from Delhi, India. (My Mozilla BugZilla > profile: > https://bugzilla.mozilla.org/user_profile?login=babhishek21%40yahoo.co.in) > > I find this idea quite interesting. A few quick questions: > > > > > Which one’s on priority - Mailman 2 or Mailman 3 for this work? > > > > The idea description was pretty clear. But just to check, “you want Mailman > to open an issue thread whenever a special marked thread on the mailing list > is posted?” Additionally, you want the reverse functionality too? > > > (Not a question) It would be better to update the description to “a tool that > will take a thread from a Mailman mailing list and turn it into a GitHub > issue”. You see a GitHub issue is already a thread unto itself. > > > Who’s going to be the mentor? Any IRC channel/nicks for rapid discussion? > > > > > > Not a proposal, but as a general overview of the task at hand: The GitHub v3 > API has a pretty simple for method for posting issues. The Mailman REST API > would work well. An important change though would be changing the admin panel > to include links and ownership details to a GitHub repo. The other task > (automatically mail a Mailman list when a repo gets a new GitHub pull > request) does not even require the API. GitHub will automatically mail the > owners, whenever a new issue is opened (a pull-request is also an issue). > Since Mailman should already have owner access, the mail could simply be > forwarded on the list. > > > > > As an extra, it would be great if we could take it to the next level and > allow for GitHub repo statistics to be posted in plain text (in a suitable > format) to mailing lists at regular intervals (as an opt-in). So now, short > concise commit logs can adorn our glorious mailing lists. > > > > > Oh… Another idea! To take it further, we could utilise GitHub’s marker/label > system for issues. I don’t know if Mailman has any “label/tag” functionality, > but it would be sweet to see priority on mailing list threads. > > > > > Some of the above things might not be possible to implement for all Issue > tracking/Repo hosting solutions, but most have industry-grade APIs. For > others, we do what we can! So wotsay? > > > > > I am sorry if I’ve not followed any format/rules. Its just that I could not > find any. 😃
If you read through the Ideas Page thoroughly, I am sure you'd find answers to most of your questions there. The Github Integration project is pretty open to new ideas and methods of integration. Also, its not just about GitHub, we would want something more generic that could be easily extended to support other Code sharing websites. -- thanks, Abhilash Raj
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
