Mailman 3 March 2014 - Mailman-Developers

Using git for mailman development during GSoC is NOT RECOMMENDED
by Terri Oda 16 Mar '14

16 Mar '14

I just added the following note to the wiki and I want to repeat it here: While it is possible to use a git mirror or other tools to use git for Mailman core and Postorius development, we DO NOT RECOMMEND USING GIT for GSoC. Merge requests need to happen on launchpad (that is the one way new code gets accepted into those projects), and previous GSoC students have found that the time required to make it all work is more than they anticipated. (We may one day switch to git, but it won't be happening this summer.) Sorry! I know our official stance for regular contributors is "use whatever as long as you can submit a launchpad merge request" but for GSoC students, you're on a short timeline that's going to be busier at the end than the beginning and experience says it's much safer to learn launchpad and use it from the get-go than risk time-consuming problems later in the process. Terri

2 1

Virtual Mailman hackathon this weekend: Mailman Suite package!
by Terri Oda 15 Mar '14

15 Mar '14

Hi all! Something we've done periodically is try to get everyone on IRC over the weekend, all working on Mailman at the same time. It's great time for people to show and get patches reviewed, chat, and get work done together. Everyone is invited! This weekend's hackathon, my plan is to try and get a Mailman suite package working. The final goal is to have it so that "pip install mailman-suite" will give you a full mailman suite install. The plan is to create the "one package to rule them all" version of Mailman Suite, with Mailman Core, Postorius, and Hyperkitty packaged together, preferably with Postorius and Hyperkitty sharing a django instance. I know basically nothing about python packaging, so help from people who do would be much appreciated (Barry?). Even the newest student is just as able to read docs and suggest things as I am on this particular project. :) I'm planning to be on #mailman on freenode around 10am PDT until 5pm PDT on Saturday the 15th, with possibly some more hours on Sunday depending on how things go and what else I have to get done. I may not manage to be actually at my computer every moment of that time since a friend is doing some filming at my house that day, but I'll try. Here's a short line of schedule in UTC. Everyone else, feel free to add your own planned hours here so we know when we overlap, or just drop by on the day if you're not sure of your schedule in advance. Terri : Sat 1700UTC - Sun 0100UTC : Mailman Suite packaging Terri

6 5

Re: [Mailman-Developers] Mailman 3 vs Groupserver vs Sympa
by Ian Eiloart 15 Mar '14

15 Mar '14

Hi Kẏra, Some additional answers, inline below. Most of your questions relate to the web archiver, and Nico has answered some of those. In order to get all the questions and answers in the same place (so people can see which questions aren’t yet answered here), I’ve rolled Nico’s comments into this reply. On 7 Oct 2013, at 03:38, Kẏra <kxra(a)riseup.net> wrote: > Hello, > > My name is Kẏra and I am the technology director of the Free Culture > Foundation as well as a campaigns organizer for the Free Software > Foundation and we're in need up upgrading our mailing lists to a more > web-friendly system. I'm doing research on newer list severs to see how > they compare. So far Groupserver seems to provide everything, but if > Mailman 3 is going to be released soon, we'd like to consider that as well. > > I'm making a comparison chart and wanted to ask about Mailman 3 (and > Postorius) features. Answers to any and all of the following with regards > to Mailman 3 + Postorius would be super helpful: > > Can you post from the web interface? yes > Is there file upload support? yes > Is there now a search feature? Can it search multiple lists? yes, yes > Are there web feeds (atom or rss)? Generated from lists? searches? threads? > files? Nico’s plugin API seems to be offering support for this. > Are posts and administration integrated into the web interface? I think that site and list administration are not part of the hyperkitty > Can you specify a posting rate restriction? I don’t know. > Is full css customization for the web interface supported? > Is css customization for the email interface supported? Hyperkitty supports "themes". I’m guessing you’ll be able to roll your own. > Is there site-side logging? (as opposed to server side) Logging (apart from web accesses) would be a Mailman responsibility. I’m not sure what you mean by "site-side", but perhaps you’re after remote reporting on a domain of yours hosted a third party at a remote site. Again, that’s possible. It could be provided through a web interface, or some other means. > Is there a link to the post in the web interface in the footer of messages? That’ll require co-operation between Mailman and the web archive. But, if the web archive URL is predictable, then I think Mailman will be able to do this. > Now that users are more than just email addresses, can you request to > contact a list member? Do you mean from their profile page, or from a list of members? > Can users have multiple email addresses? Yes, that’s a part of users being more than just email addresses. > Are there profile pages where you can see a summary of their latest posts? yes > Can the web interface hide quoted text? yes > Are usage statistics provided? The Hyperkitty change log for 0.1 alpha says "show basic list info and metrics". Certainly the Mailman 2 logs provide enough information from which useful usage stats could be derived. If Hyperkitty doesn’t provide the stats that you want, you’ll likely be able to get them from the log files. > Thanks! > > Also, did Mailman 2 already support LMTP and virtual domains or are those > new? They’re new. Mailman 2 did have partial support of virtual domains, but there was a restriction whereby no two domains could have a list with the same name: so I can’t imagine that this would be useful. > > Best, > Kẏra > > -- > Board of Directors, Free Culture Foundation: www.freeculture.org > Campaigns Organizer, Free Software Foundation: www.fsf.org > > Blog: http://kxra.info - StatusNet Microblog: http://identi.ca/kxra > Email: kxra(a)freeculture.org - SMS: +1.617.340.3661 > Jabber/XMPP: kxra(a)riseup.net - IRC: kxra @freenode @oftc @indymedia > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)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/iane%40sussex.ac… > > Security Policy: http://wiki.list.org/x/QIA9 -- Ian Eiloart Postmaster, University of Sussex +44 (0) 1273 87-3148

2 1

Getting mentor attention [was: Mailman SNMP support]
by Stephen J. Turnbull 14 Mar '14

14 Mar '14

Nitin Agarwal writes: > Here its Nitin Agarwal, an open source Software developer and > enthusiast. Hi, pleased to meet you. I'm belatedly replying to the list, and at length, as there are other students in your situation. I hope it helps. First off, I saw you talked to Terri on IRC. Much as I hate to burden Terri, that is the right thing to do if you're not getting attention to your proposal, especially from persons who proposed or volunteered to mentor it. If at all possible, try to grab GSoC people on IRC (or by email) in the following order: 1. Any other mentor or active developer, to get comments first. 2. Barry. 3. Terri or Florian. 4. Jessica (real last resort). Contact info for the above is on the "Ideas" page. Barry isn't official in GSoC, but he's head of the Mailman project and a ranking demi-god in the Pytheon. Also crazy busy, so you may get a polite brushoff. OTOH, he can probably solve Mailman problems in half the time of anybody else. And if Barry asks for help, someone will respond. Terri and Florian are PSF org admins, not just Mailman IIUC. Crazy busy, too, but dealing with problems is their job as org admin. As org admins, to some extent they can knock heads. You don't really want that, except as a last resort. Jessica is PSF org admin, with no specific interest in Mailman. A really last resort, because it implies Terri and Florian are asleep at the wheel. N.B. They all *like* talking to people when they've got time. Don't be *afraid* to talk to them. But it's better to spread yourself around (or as the Japanese say, develop a wide face) and get to know more people in the project, especially at the start. > I am looking forward to contribute to Mailman in the upcoming > Google Summer of Code 2014 through the Mailman SNMP Support Project > idea. I have an experience with the open source software > development and tools used. This is a "good enough" short self-introduction. However, it doesn't shine. It's like providing a numerical answer on a math test, without showing your work. (Boy do I hate it when students do that....) Specifying languages (and implementations), maybe applications and libraries, related to the project that you have worked with, or especially "on", polishes the image. Mention projects (an URL to your github page is just another numerical answer -- tell us about your work!) But keep it short (yes, I know it's difficult to do both). Image is important -- we mentors are all human, bright shiny things attract our attention. That's part of why we need org admins -- not everybody has image skills[1], so somebody has to go looking for and polishing up those diamonds in the the rough. But you can better your chances by not depending on the org admins to get attention for your proposal -- do it yourself. > I have an indepth knowledge of SNMP protocol and an understanding > of the concepts specified in the SNMP RFC 1157. Although I'm willing to co-mentor this project, when you first posted I was able to expand "SNMP" but that was the extent of my knowledge. (Standards geeking is one of the things I'm good at, I'm pretty sure I can catch up. :-) I had no clue about why Mailman would want it or who requested it or who would mentor it. So I didn't respond. The two "whos" are our bad (they should be on the "Ideas" page, partly remedied now). But it's important that *you* explain *why* you chose that feature. It's OK to just say "it's in my toolkit" (and do be honest about your motivations -- mentoring is a "trust" relationship). But, again, your proposal shines when you tell us why *we* (or our users) want it. So you (or any student) can greatly improve your chances of getting someone to engage by telling us "why" we want it. You do that by focusing on the *user requirements* rather than on the *design and implementation* ("use this protocol" is design; "use this library" is low-level design, aka a plan for implementation). Everybody on this list is a Mailman *user* (broadly defined as list members, list admins of several flavors, and site admins), but not all are *developers*. If you can get some users saying "hey, *I* could *really* use that feature," it's more attractive to the developers and mentors (and we always have more desirable features than slots). But remember, users often don't know the buzzwords like SNMP (or even SMTP, and RFC numbers are quite arbitrary). Concretely, what are the benefits to subscribers and/or admins? Tell stories about situations where this feature would help. Describe how it would operate (from the user's viewpoint, not the protocol itself). N.B. This advice isn't universal. In some projects, mentors are core developers who are looking for someone "just like them", who knows the protocol and just wants to dive in and implement a pre-specified feature. (That's typical for compiler optimizations, for example.) But I think it's pretty good advice for Mailman at the present time. ***** About this specific project, my initial reaction was "we *have* an NMP" (usually called "the REST interface"). Why do we need another network management protocol, even if it's "simple"? Remember, "there should be one-- and preferably only one --obvious way to do it" is a fundamental principle of design for Python developers.[2] What does SNMP do for us that the REST interface doesn't? Pop quiz (relevant to that last question): What statement in Sec. 1.3 of RFC 3411 immediately caught my eye? Hint: which letter in "FCAPS" caught my eye? (To readers not interested in implementing SNMP in Mailman as a GSoC intern: *don't* answer on-list!! This quiz is for prospective interns on the SNMP project!) Why are they interesting? Do you propose to replace the RESTful interface, or to have two interfaces? (This question is not a quiz, it's a research question -- quite possibly you may finish your project and still not have a fully satisfactory answer to that.) Another question: RFC 1157 is labelled "historic". It's been obsoleted several times. I realize that the current set of related RFCs counts at least 5 (what's "simple" about that?!), but ISTM there are important reasons why we really want the modern versions. Are you familiar with the important changes in goals for the newer RFCs? Footnotes: [1] Note that "English is my second language" is not an excuse. Every post I've seen so far is perfectly understandable, and nobody needs to be ashamed of their English. The issue is that working on Mailman at the present time requires understanding user requirements, so do the best you can to tell stories about your project that end with users living happily ever after! Yes, I know, second languages cost. I work in a second language that is easily the most difficult ever invented -- Japanese. But (unless you're very fortunate in finding a mentor who speaks your language), you will have to get over that, so I discount the cost -- you've already decided to pay it. [2] If you're not familiar with these programming proverbs, type "python -m this".

3 2

GSoC 2014 : Proposal for the Mailman CLI project
by Rajeev S 14 Mar '14

14 Mar '14

Hi, I have submitted a proposal for the Mailman CLI project through melange.You can find it here https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2014… (Organisation view only) I have gone through the suggestions by Stephen as comments to the proposal and revised the proposal accordingly. http://myfossblog.blogspot.in/2014/03/gsoc-proposal-to-gnu-mailman.html *Regards,Rajeev S* *Government Engineering College,Thrissur* *http://rajeevs.tk <http://rajeevs.tk>*

1 0

Re: [Mailman-Developers] GSOC 2014
by Abhilash Raj 14 Mar '14

14 Mar '14

Hi Milap, Thanks for choosing Mailman. You should get started by reading documentation online here[1] and then trying to setup your own mailman installation. If you have any problems in it you are free to ask any questions here or at #mailman on freenode irc for quick replies. About the projects you are interested in, I would suggest you to choose one project out of the two you mentioned as get started on your proposal asap. There are other students interested in your project as well and you should check archives of this mailing list and go through the discussions. On Friday 14 March 2014 01:14 AM, Milap Bhojak wrote: > Hello, > > I'm Milap Bhojak. I'm looking for Gsoc this year. PSF is the one of my > favorite organization (Of course) for every Py dev. :). i'm Contributor at > VideoLAN (VLC Media Player). i'm interested in Continuous integration tool > for the Mailman suite and Mailman command line client projects could any > one guide me ? > [1]: http://pythonhosted.org/mailman/src/mailman/docs/START.html [2]: http://www.mail-archive.com/mailman-developers%40python.org/ thanks, Abhilash Raj

1 0

Re: [Mailman-Developers] [GSoC 2014] Cordova/Android App for GNU Mailman Admin Interface
by Florian Fuchs 14 Mar '14

14 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/13/2014 05:41 AM, Bhargav Golla wrote: > Regarding your second comment, I indeed took Terri's suggestion > about Intel XDK and am evaluating it while I am writing the > proposal. And I have missed out Postorius responsive UI project > idea. Thanks for pointing it out. The two project ideas ("Cordova app" vs. "Postorius responsive") are similar to some extend, but with significant differences. Let me highlight some of them: Both projects will make you write a good amount HTML/CSS/JS code, as Cordova also uses these technologies for the user interface. Ideally (if both projects are implemented - which isn't very likely) the UI should not be much different - no matter if you open Postorius on a phone's browser or use the native Cordova app. 1. Postorius responsive The Postorius responsive project builds on an existing (Django) back-end that is ready to be used. You might need to implement *some* backend features, but (in contrast to the Cordova project) especially the authentication/authorization part is something you will not have to worry about because the framework already takes care of this. You can concentrate on the interesting UI parts and make everything work nicely on a variety of different devices. Oh, but please don't underestimate the amount of (really very interesting) work you can put into making a site really usable with either keyboard, mouse and fingers. 2. Cordova app The Cordova project is different in that it doesn't build on an existing underlying back-end, which means you will have to take care of the communication with the core, as well as of authorization. Mailman's REST API is mainly built for local use, giving you wide-ranging permissions by default (meaning: if your credentials are ok, you can do everything). It's definitely not advisable to expose it directly to a phone app and then let this app manage the permissions (because that way all users could make themselves admins by manipulating the app's source code). So what's needed is a layer in between (and controlled by the site, not the app). This could be implemented as part of Postorius, but it could theoretically also be something else on top of the core's REST API. Which one would first have to be discussed (there are good arguments to be made for both scenarios). So, in the end, the Cordova project will not be a pure app project. Hope that helps. Cheers Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTIhdvAAoJEEceGbPdavl7LwAH/2tCr/NgpaD1PbygPEV1LVVP 9PGybptYEFX95eBZoZ6ZXGdOM5y1emBiNhvnoiQT8ciGYnnfqFo9yG+vlHUBbvnp HEDvzERoYPmZs7uHTLslvqXxpoPeFNbB8Zqk9bWKZdnCa8IRNmwCj87XzKYzMCYC PyMmpSx3/ypjYJOoyGDsDtJkSmKKX+ZyzETHL+A/N1rA/06Ic2xNhWlyqe64GDu/ N2D+wo2Qw0+DQa80733HXdHoJn/7Us4w0ed1TU58PAbRBMBhfPi69yTOH4LRgWeS Kq7EmyaEpKOl0n12sOQv65BOxC6Y5Oryka2wkefgTsSzzTIQo8jx8BHKXXXWJww= =eMLU -----END PGP SIGNATURE-----

1 0

GSOC 2014
by Milap Bhojak 14 Mar '14

14 Mar '14

Hello, I'm Milap Bhojak. I'm looking for Gsoc this year. PSF is the one of my favorite organization (Of course) for every Py dev. :). i'm Contributor at VideoLAN (VLC Media Player). i'm interested in Continuous integration tool for the Mailman suite and Mailman command line client projects could any one guide me ? -- Thanks, Milap Bhojak | Google Developers Group - Gandhinagar, Google India | milapbhojak.exe(a)gmail.com | +91-9898855075

1 0

Re: [Mailman-Developers] [GSoC 2014] Cordova/Android App for GNU Mailman Admin Interface
by Stephen J. Turnbull 13 Mar '14

13 Mar '14

Bhargav Golla writes: > guess the culture varies from organization to organization Thank you for pointing this out. Indeed it does. ASF (and the PSF for that matter) have a lot more applicants, and at least the PSF is using a generic channel -- core-mentorship -- for GSoC and OPW interns. In those cases it makes a lot of sense to clearly indicate what the post is for, and who. In Mailman it happens to be the case that this list, although it is the generic developers list, is relatively low traffic, except at GSoC time. So we know what you're going to talk about. :-) > and I should have been wary of this or should have followed usual > email etiquette. It was wrong on my part I certainly wouldn't say "wrong", as you apparently are already well- aware of the etiquette issues. You did your best. We can't ask for more than that given varying culture and needs. (Heck, I myself didn't clean up the headers....) Steve

1 0

Re: [Mailman-Developers] [GSoC 2014] Cordova/Android App for GNU Mailman Admin Interface
by Stephen J. Turnbull 13 Mar '14

13 Mar '14

Bhargav Golla writes: > I hope my mail hasn't missed your attention. I would be very much > obliged if someone could answer this question so that I can go > ahead and write proposal. First, it's impolite to send mail to specific people just because they're answered you before, unless they are specifically interested in mentoring your project or have requested personal mail. I don't think either is true (according to the wiki, there are no prospective mentors for this project -- I'm sure there are some, but they're not identified). Everybody reads this list, and by addressing them specifically you may be sending them duplicates. Note: no harm done this time, but you will be a much more valuable developer if you become sensitive to these "marginal" "people skills". Second, you yourself have not responded to a somewhat detailed comment from Terri about using HTML5. I for one have been waiting for that. See also the "Postorius Responsive UI" project. Third, "there's not much here to comment on" is all I really have to say. From the Subject I can see that you're interested in a handheld interface. From the text you quote, I see you have a *very* basic grasp of the requirements of web protocols for this application. You probably know a heck of a lot more -- but that's all I can confirm from your posts. The way you ask is problematic. On the one hand, a GSoC proposal is not a homework for school. There are no "right" answers, only good ones and better ones. And you don't have to give a superior answer immediately to qualify, only show promise of heading in the right direction. (Of course, there are more students than slots, so you also have to show more promise than others. But you have another week or so to improve, and the delta can be in your favor.) On the other, it's not *one* question. Rather, it has a strong whiff of "please write half my proposal (the hard half) for me". So just write your proposal so there's something to actually comment on. All that said, "login screens" are way clunky for modern handheld apps. Users expect a smooth convenient experience. Second, that experience does not include entering passwords on a frequent basis. You should look into including TLS authentication. These need not be present in the initial design, and maybe they won't even be in your delivered product. But you should think in terms of a design that allows easy upgrades to the UI. Steve > > Thanks > > > On Mon, Mar 10, 2014 at 9:23 AM, Bhargav Golla <bgolla(a)g.clemson.edu> wrote: > > > Hello > > > > I have gone through the Admin interface and all functions that can be > > achieved with the REST API. I intend to have a login screen where a user > > can enter URL for the REST API endpoint, REST Username and password. We > > will use this to subsequent authenticate all requests made to fetch > > subscribers list, domains list, etc. > > > > I was wondering if I could get some feedback on this. I will start writing > > my proposal based on this starting point and list out what all I would > > features I would be implementing during the period of GSoC. > > > > Regards > > > > > > On Wed, Mar 5, 2014 at 10:32 AM, Bhargav Golla <bgolla(a)g.clemson.edu>wrote: > > > >> Thanks. I would have probably missed it out the first time. I will go > >> through the web UI and also the documentation of REST API to understand > >> what all functions need to be implemented in the admin interface for a user. > >> > >> Regards > >> > >> > >> On Wed, Mar 5, 2014 at 10:25 AM, Rajeev S <rajeevs1992(a)gmail.com> wrote: > >> > >>> Hi, > >>> > >>> You will be asked for the create user prompt only the first time you run > >>> syncdb.That's why you don't see it now. > >>> > >>> Once the DB is created, only new tables, specified via django models, > >>> get added to DB during the syncdb. > >>> > >>> > >>> *Regards,Rajeev S* > >>> *Government Engineering College,Thrissur* > >>> *http://rajeevs.tk <http://rajeevs.tk>* > >>> > >>> > >>> On Wed, Mar 5, 2014 at 8:47 PM, Bhargav Golla <bgolla(a)g.clemson.edu>wrote: > >>> > >>>> Hi Rajeev > >>>> > >>>> I wasn't asked if I wanted to create a super user when I executed > >>>> python manage.py syncdb. This was the output I got with syncdb: > >>>> Creating tables... > >>>> Installing Custome SQL... > >>>> Installing indexes... > >>>> Installed 0 object(s) from 0 fixture(s) > >>>> > >>>> I tried python manage.py createsuperuser and was able to login with > >>>> details I provided there. > >>>> > >>>> Thanks for your help. > >>>> > >>>> Regards > >>>> > >>>> > >>>> On Wed, Mar 5, 2014 at 10:00 AM, Rajeev S <rajeevs1992(a)gmail.com>wrote: > >>>> > >>>>> Hi Bhargav, > >>>>> > >>>>> You will be asked whether to *add a superuser* during *syncdb*. If > >>>>> you answered no to that, do *python manage.py createsuperuser * and > >>>>> use that username and password to login. > >>>>> > >>>>> > >>>>> *Regards,Rajeev S* > >>>>> *Government Engineering College,Thrissur* > >>>>> *http://rajeevs.tk <http://rajeevs.tk>* > >>>>> > >>>>> > >>>>> On Wed, Mar 5, 2014 at 8:05 PM, Bhargav Golla <bgolla(a)g.clemson.edu>wrote: > >>>>> > >>>>>> Hi Abhilash > >>>>>> > >>>>>> If you mean the last step of installation where we do cd > >>>>>> postorius_standalone;python manage.py syncdb, I wasn't asked for any > >>>>>> username/password. I checked the settings.py and it doesn't have any > >>>>>> specific default username/password. > >>>>>> > >>>>>> And the http://localhost:8001/3.0 worked for me. > >>>>>> > >>>>>> > >>>>>> On Wed, Mar 5, 2014 at 9:22 AM, Abhilash Raj <raj.abhilash1(a)gmail.com > >>>>>> >wrote: > >>>>>> > >>>>>> > Hi Bhargav, > >>>>>> > > >>>>>> > On Wednesday 05 March 2014 07:36 PM, Bhargav Golla wrote: > >>>>>> > > Thanks for that change Rajeev. I was able to get the Web UI up and > >>>>>> > running. > >>>>>> > > I was trying to find out the default Username and password for > >>>>>> this but > >>>>>> > was > >>>>>> > > unable to. When I was exploring docs in mailman.client and some > >>>>>> config > >>>>>> > > files in mailman, I found that the default username and password > >>>>>> for > >>>>>> > admin > >>>>>> > > is restadmin and restpass. Tried that and was out of luck there > >>>>>> too. > >>>>>> > Could > >>>>>> > > you help me with the default username and password details? > >>>>>> > > >>>>>> > While setting up Postorius(the web UI) when you do 'python manage.py > >>>>>> > syncdb' for the first time, it asks you to create admin. You can > >>>>>> log in > >>>>>> > using those credentials. 'restadmin' and 'restpass' are the > >>>>>> credentials > >>>>>> > for the mailman rest server. > >>>>>> > > >>>>>> > > Also, there is a using.txt doc in mailman.client which says we > >>>>>> can make > >>>>>> > the > >>>>>> > > REST requests by connecting to http://localhost:9001/3.0 using > >>>>>> username > >>>>>> > and > >>>>>> > > password. Should the URL be http://localhost:9000/3.0 for this > >>>>>> example > >>>>>> > or > >>>>>> > > would it be any different? > >>>>>> > > >>>>>> > AFAIK it is 'http://localhost:8001/3.0'. (Try it once. If I am > >>>>>> wrong > >>>>>> > please someone correct me) > >>>>>> > > >>>>>> > > > >>>>>> > > Thanks > >>>>>> > > > >>>>>> > > > >>>>>> > > On Mon, Mar 3, 2014 at 1:38 PM, Rajeev S <rajeevs1992(a)gmail.com> > >>>>>> wrote: > >>>>>> > > > >>>>>> > >> Hi Bhargav, > >>>>>> > >> > >>>>>> > >> Just do *mailman start*, without the bin. > >>>>>> > >> > >>>>>> > >> I have edited the wiki. > >>>>>> > >> > >>>>>> > >> > >>>>>> > >> *Regards, Rajeev S* > >>>>>> > >> *Government Engineering College,Thrissur* > >>>>>> > >> *http://rajeevs.tk <http://rajeevs.tk>* > >>>>>> > >> > >>>>>> > >> > >>>>>> > >> On Mon, Mar 3, 2014 at 10:37 PM, Bhargav Golla < > >>>>>> bgolla(a)g.clemson.edu > >>>>>> > >wrote: > >>>>>> > >> > >>>>>> > >>> Thanks Barry and Terri for your feedback. > >>>>>> > >>> I was trying to install Postorius locally and analyze what all > >>>>>> would be > >>>>>> > >>> required in a mobile app for Admin. Doing the same, I have hit a > >>>>>> > >>> roadblock. > >>>>>> > >>> I am using the wiki provided here[1]. I tried to install > >>>>>> mailman using > >>>>>> > >>> "set > >>>>>> > >>> up sources" part of the wiki. Though python setup.py install > >>>>>> executes > >>>>>> > >>> without any errors, I am unable to see the folder bin/ in the > >>>>>> same > >>>>>> > >>> directory. So, even though I proceed with further setup, I am > >>>>>> getting a > >>>>>> > >>> "Mailman REST API not available. Please start mailman core" on > >>>>>> my > >>>>>> > >>> localhost:8000 webpage. Could anyone help me here? > >>>>>> > >>> > >>>>>> > >>> [1] > >>>>>> > >>> > >>>>>> > >>> > >>>>>> > > >>>>>> http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI… > >>>>>> > >>> > >>>>>> > >>> Thanks > >>>>>> > >>> > >>>>>> > >>> > >>>>>> > >>> On Sun, Mar 2, 2014 at 1:18 AM, Terri Oda <terri(a)toybox.ca> > >>>>>> wrote: > >>>>>> > >>> > >>>>>> > >>>> > >>>>>> > >>>> On 2014-02-28, 7:36 AM, Bhargav Golla wrote: > >>>>>> > >>>> > >>>>>> > >>>>> I have a few questions regarding this idea. > >>>>>> > >>>>> 1. I intend to develop it on Cordova since it will help in > >>>>>> porting > >>>>>> > the > >>>>>> > >>> app > >>>>>> > >>>>> easily to multiple platforms. Were there any ideas in this > >>>>>> directions > >>>>>> > >>>>> regarding going native or hybrid? > >>>>>> > >>>>> > >>>>>> > >>>> > >>>>>> > >>>> Personally, I'd prefer if we went hybrid and had an html5 > >>>>>> webapp that > >>>>>> > >>>> could be used straight over the web for mobile users who don't > >>>>>> want to > >>>>>> > >>>> install an app, with Cordova used to build the individual > >>>>>> platform > >>>>>> > >>> apps. I > >>>>>> > >>>> may not be the mentor on this one, though, so I'm happy to > >>>>>> defer to > >>>>>> > >>> whoever > >>>>>> > >>>> the final mentor is on this front. > >>>>>> > >>>> > >>>>>> > >>>> Incidentally, I've been using Intel's XDK for building Cordova > >>>>>> apps > >>>>>> > >>> lately > >>>>>> > >>>> and highly recommend it for quick testing on various platforms > >>>>>> and > >>>>>> > >>> screen > >>>>>> > >>>> sizes. I've found it a very useful tool, and not just because > >>>>>> I work > >>>>>> > >>> for > >>>>>> > >>>> Intel now! > >>>>>> > >>>> > >>>>>> > >>>> 2. Can I assume that all mailing lists built by Mailman > >>>>>> support the > >>>>>> > >>> REST > >>>>>> > >>>>> interface? Also, I have tried to see if I can get JSON > >>>>>> responses and > >>>>>> > I > >>>>>> > >>> am > >>>>>> > >>>>> unable to by adding a HTTP Accept Header to take > >>>>>> "application/json". > >>>>>> > >>> Am I > >>>>>> > >>>>> doing anything wrong or is JSON not implemented? > >>>>>> > >>>>> > >>>>>> > >>>> > >>>>>> > >>>> I don't know the answer to this off the top of my head: Barry? > >>>>>> > >>>> > >>>>>> > >>>> > >>>>>> > >>>> 3. As a starter, could I ignore internationalization for > >>>>>> GSoC, but > >>>>>> > >>>>> implement interface in such a way as to be able to > >>>>>> internationalize > >>>>>> > it > >>>>>> > >>>>> easily? > >>>>>> > >>>>> > >>>>>> > >>>> > >>>>>> > >>>> We don't expect you to actually translate anything, don't > >>>>>> worry. :) > >>>>>> > But > >>>>>> > >>>> you should definitely build as much as possible so that > >>>>>> > >>>> internationalization will be easy: make sure there's a quick > >>>>>> way to > >>>>>> > get > >>>>>> > >>> a > >>>>>> > >>>> list of strings that need translation, at least. Some of the > >>>>>> strings > >>>>>> > >>> may > >>>>>> > >>>> be already translated in other components of Mailman, so you > >>>>>> may be > >>>>>> > >>> able to > >>>>>> > >>>> get some translations to use to test if you have time at the > >>>>>> end of > >>>>>> > the > >>>>>> > >>>> summer for internationalization. > >>>>>> > >>>> > >>>>>> > >>>> Terri > >>>>>> > >>>> > >>>>>> > >>>> > >>>>>> > >>> > >>>>>> > >>> > >>>>>> > >>> -- > >>>>>> > >>> Bhargav Golla > >>>>>> > >>> M.S Computer Science > >>>>>> > >>> Github <http://www.github.com/bhargavgolla> | > >>>>>> > >>> LinkedIN<http://www.linkedin.com/in/bhargavgolla> > >>>>>> > >>> | Website <http://www.bhargavgolla.com/> > >>>>>> > >>> _______________________________________________ > >>>>>> > >>> Mailman-Developers mailing list > >>>>>> > >>> Mailman-Developers(a)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/rajeevs1992%40gm… > >>>>>> > >>> > >>>>>> > >>> Security Policy: http://wiki.list.org/x/QIA9 > >>>>>> > >>> > >>>>>> > >> > >>>>>> > >> > >>>>>> > > > >>>>>> > > > >>>>>> > > >>>>>> > -- > >>>>>> > Abhilash Raj > >>>>>> > > >>>>>> > > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Bhargav Golla > >>>>>> M.S Computer Science > >>>>>> Github <http://www.github.com/bhargavgolla> | > >>>>>> LinkedIN<http://www.linkedin.com/in/bhargavgolla> > >>>>>> | Website <http://www.bhargavgolla.com/> > >>>>>> _______________________________________________ > >>>>>> Mailman-Developers mailing list > >>>>>> Mailman-Developers(a)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/rajeevs1992%40gm… > >>>>>> > >>>>>> Security Policy: http://wiki.list.org/x/QIA9 > >>>>>> > >>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> Bhargav Golla > >>>> M.S Computer Science > >>>> Github <http://www.github.com/bhargavgolla> | LinkedIN<http://www.linkedin.com/in/bhargavgolla> > >>>> | Website <http://www.bhargavgolla.com/> > >>>> > >>> > >>> > >> > >> > >> -- > >> Bhargav Golla > >> M.S Computer Science > >> Github <http://www.github.com/bhargavgolla> | LinkedIN<http://www.linkedin.com/in/bhargavgolla> > >> | Website <http://www.bhargavgolla.com/> > >> > > > > > > > > -- > > Bhargav Golla > > M.S Computer Science > > Github <http://www.github.com/bhargavgolla> | LinkedIN<http://www.linkedin.com/in/bhargavgolla> > > | Website <http://www.bhargavgolla.com/> > > > > > > -- > Bhargav Golla > M.S Computer Science > Github <http://www.github.com/bhargavgolla> | > LinkedIN<http://www.linkedin.com/in/bhargavgolla> > | Website <http://www.bhargavgolla.com/> > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)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/stephen%40xemacs… > > Security Policy: http://wiki.list.org/x/QIA9

2 1