[Mailman-Developers] GSoC 2015: brainstorming ideas suitable for beginners?

[Andrew Stuart]

>>> [1] The "additional user info" bit possibly re-raises the big question of a central user data store for all Mailman components, which will clearly not be solved as part of a GSoC project, especially a beginner-friendly one. But we do already have a little bit of info, the user's email address and the gravatar (if there is one). So all we'd have to store is an opt-in flag somewhere in the Django-DB.

I have implemented a central data store into the REST proxy server.  It’s a simple table structure as follows:

————————————————————————————————————————————————————————————————————————
resource_type  |  resource_id   |   private/public  |  key   |    value 
————————————————————————————————————————————————————————————————————————
user
list
domain
server

User access permissions for the data rows is the same as access to the resource_type & resource_id

It’s workable as a part of the auth proxy but feels like it would fit better in the Mailman core database since the data is so tightly bound to Mailman resources.  It’ll need an effective replication mechanism to ensure consistency with Mailman which is a challenge I’m not relishing solving.

as





On 18 Feb 2015, at 4:42 am, Florian Fuchs <f at florianfuchs.com> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Am 17.02.2015 um 10:03 schrieb Terri Oda:
> I'd love some help brainstorming some actual beginner-friendly
> ideas, though, because I'm currently all idea'd out.  Anyone want
> to suggest some simpler things they'd like to see in Mailman that
> we could maybe put on the list?

Just from the top of my head, either as a combination of the two or as
single projects (if fleshed out a bit further):

- - A Dashboard for Admins/Owners/Moderators: A single page that lists
all to dos in one place (subscription requests, held messages).
Probably useful for owners/moderators of multiple lists.

- - Subscriber pages: Let users opt-in to show their membership to other
list members. Possibly along with some additional user information[1].
This could be useful for more private lists if you want to get an idea
who your audience is.


Florian


[1] The "additional user info" bit possibly re-raises the big question
of a central user data store for all Mailman components, which will
clearly not be solved as part of a GSoC project, especially a
beginner-friendly one. But we do already have a little bit of info,
the user's email address and the gravatar (if there is one). So all
we'd have to store is an opt-in flag somewhere in the Django-DB.




> 
> Suggesting and idea does not mean you have to volunteer to mentor
> them, although I'm always looking for new mentors too!
> 
> Terri
> 
> _______________________________________________ Mailman-Developers
> mailing list Mailman-Developers at 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/f%40florianfuchs.com
> 
> 
> 
> Security Policy: http://wiki.list.org/x/QIA9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJU432YAAoJEEceGbPdavl7CqEH/AvOLwc+qyWkmNw6Tahm6Jjb
IHVnz4yv4sTFmdB9iqYXkOQqt7XgpEoIYUZwV+j7+vltDSYSh2qecKyVyQjBkEUC
wc7hU8/czOw2E/I3MG1siRzCGeekGJSTFXf2NoKksUNca9DUQe0leNKs1VWXwaX5
uAsyitJxaiPJIsrKHeVhGO6g4rSmqBMi+Q+HTaBIZQqZZd1Qh7ZgUV4qXFuTjUXw
D4Ae20sdFAdLD412e3LrgI58JiXRNIHBfWzN1Zg0RoY95rw/AuDafrlPT37I2E7O
mahaaJAJrmPO3EimeDPmj1TTV7NWOpaU9Vlzd6H5BX4KweUxAaafYHFrkYXN/pU=
=L+aD
-----END PGP SIGNATURE-----
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers at 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/andrew.stuart%40supercoders.com.au

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