[Mailman-Developers] Gitlab integration, GSOC'16
Terri Oda
terri at toybox.ca
Mon Feb 29 08:41:27 EST 2016
On 2016-02-28 1:34 PM, aahan bhatt wrote:
> Please explain about the gitlab integration in layman terms. I would like
> to contribute to the project.
Gitlab integration can mean a lot of things, and we've left this
particular project pretty open to see what people will suggest.
The tweet linked talks about moving a discussion from a mailing list to
a bug tracker. So imagine that you have a bunch of people discussing an
issue on a mailing list and after a few posts someone says "hm, that
configuration didn't work the way I expected, this sounds like a bug,
maybe we should file it" -- we want a way to dump the whole discussion
into a bug so when someone goes to fix it they have all the information.
You'd need to think a bit about privacy (were the mailing list posts
public? what about the bug tracker?) and relevance of information (what
if I only want some of the posts? what if I want to link the discussion
but only provide a summary?) to go from the idea of "make it easier to
file bugs using information from a mailing list discussion" to an actual
workable interface for doing that, but that's the core of it.
If you want to understand the whole gitlab integration idea better
beyond that one use case, try brainstorming a little bit about how the
pieces could work together. How could a mailing list integrate better
with a bug tracker? How could it integrate better with merge requests?
What information would people want to pass from one system to the
other and why?
For an example you might want to take a look at idea #27 on this page:
http://blog.linuxgrrl.com/2012/03/14/mailman-brainstorm-2/
More information about the Mailman-Developers
mailing list