[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mailman-developers
Subject:    Re: [Mailman-Developers] Student looking to contribute towards GNU Mailman
From:       Adam McGreggor <adam () amyl ! org ! uk>
Date:       2016-01-02 15:03:13
Message-ID: 20160102150313.GE21217 () hendricks ! amyl ! org ! uk
[Download RAW message or body]

On Fri, Jan 01, 2016 at 02:39:35AM +0900, Stephen J. Turnbull wrote:
> https://gitlab.com/mailman/mailman/issues/62
> https://gitlab.com/mailman/postorius/issues/5
> 
> Neither seems to suggest that anybody is actually working on this
> project.  Note that the issues are titled "User Profile Pages" rather
> than "Subscriber Profile Pages" -- searching for appropriate issues is
> an art.  Don't kill yourself trying to do an exhaustive search or
> coming up with the perfect keywords.
> 
> If you decide to work on this, come up with a summary of what *you*
> want to do (it may help to refer to the existing issue descriptions),
> and post it as an RFE (request for enhancement), most likely on the
> Postorius tracker.  That will allow others interested in the project
> (both potential users and developers) to find you.  Mention that you
> are working on the project, and link to the existing issues.

For something as common (in principle, at least) as these, I think it
might be useful in these posts *as RFEs), to commit an outline/spec 
(so others can PR against it), which also considers the merits of
Things Already Written, and what (if any) enhancements etc they might
need (and I suspect they will, as noted, things are scattered about
with separate components, rather than a collexion of microservices
that plugin).

It strikes me that something like this already exists, and may be even
as far as 70% there (i.e. general functionality that works well, is
well maintained & documented). It also feels (in my mind) a more
open-source way of working, and could benefit from receiving updates
etc from 'upstream'.

> A bit of advice: I tend to disagree with Our Fearless Leader: I think
> there's more of a role for "core" in this.  Specifically,
> discoverability of resources.  Resources are spread across the three
> main components, and the list archives at least will have multiple
> implementations in common use.

"Under which project do I raise this bug report?"
"oh look, duplication of issues…"
"I just want it all working to best practice".

-- 
"The English people are like the English beer--
 froth on top, dregs at the bottom; the middle, excellent." 
    -- Voltaire
_______________________________________________
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/mailman-developers%40progressive-comp.com


Security Policy: http://wiki.list.org/x/QIA9


[prev in list] [next in list] [prev in thread] [next in thread]