If I run the mailman command it keeps creating “var” directories in whatever
the current directory is.
Is that intentional?
thanks
___
Mailman-Developers mailing list
Mailman-Developers@python.org
Where can I find the documentation that explains the required configuration for
cron in Mailman 3?
thanks
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ:
,
Yes, that's intentional.
The var directory setting is set to current directory by default.
You can set it to a fixed directory by modifying the var_dir setting in
mailman.cfg.
Sent from my BlackBerry 10 smartphone.
Original Message
From: Andrew Stuart
Sent: Thursday 4 December 2014 06:47
:
Hi Andrew,
On Sat, Dec 6, 2014 at 12:04 PM, Andrew Stuart
andrew.stu...@supercoders.com.au wrote:
When I run “mailman info”, it creates a “var” directory in the current
directory.
Yes this is the default behavior when you don't specify the paths explicitly in
your mailman.cfg
You can see
, at 6:31 pm, Abhilash Raj raj.abhila...@gmail.com wrote:
Hi Andrew,
On Sat, Dec 6, 2014 at 12:04 PM, Andrew Stuart
andrew.stu...@supercoders.com.au wrote:
When I run “mailman info”, it creates a “var” directory in the current
directory.
Yes this is the default behavior when you don't specify
thanks
Andrew
___
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:
Hello,
Referring to transcript below, the word Aurélien seems to be causing a unicode
error when setting up mailman client.
When I cut it out, it works.
thanks
(venv2.7)ubuntu@server01:~$ bzr branch lp:mailman.client
You have not informed bzr of your Launchpad ID, and you must do this to
I want to run the REST tests against my live Mailman server with its Postfix
mail server and Postgres database, via:
nose2 -v -P rest
After many (many) hours of digging deep and figuring out how it works, I
suspect at this stage that maybe the tests set up their own mock servers? If
so, I’m
that’s not a short route. :-)
Trying to bend the existing tests to meet my needs is looking harder than I
have time to deal with.
Andrew
On 12 Dec 2014, at 8:27 am, Barry Warsaw ba...@list.org wrote:
On Dec 12, 2014, at 07:52 AM, Andrew Stuart wrote:
I want to run the REST tests against my
or correct the host
and port number.
Andrew
On 12 Dec 2014, at 11:34 am, Barry Warsaw ba...@list.org wrote:
On Dec 12, 2014, at 08:35 AM, Andrew Stuart wrote:
I’m writing an authenticating proxy for the Mailman REST API and want to make
sure everything works as expected against real
On 12 Dec 2014, at 12:45 pm, Stephen J. Turnbull step...@xemacs.org wrote:
Andrew Stuart writes:
I’m writing an authenticating proxy for the Mailman REST API and
want to make sure everything works as expected against real
infrastructure (Postgres/Postfix/Sqlalchemy/Falcon).
Determining
| -+
| |
+-+
On 17 Dec 2014, at 12:08 am, Stephen J. Turnbull step...@xemacs.org wrote:
Andrew Stuart writes:
Thanks for the guidance - I’ll have to admit I don’t know much
about how to do such things
This is as much gathering my thoughts on research. Anyone with questions or
comments or ideas welcome. Just raw ideas at this stage.
The goal is to build user level REST authentication for Mailman on top of the
existing REST API.
Mailman user REST authentication/authorization.
Use
Is there anything I can do to help with these? If there’s a task list maybe I
can work out what I could do.
This means I must now port HyperKitty and Kittystore to Python3, check that
we don't use Py2-only libraries, etc.
And mailman.client must be ported too, since it does import stuff from
If it is released to version 1.0 with support for Python 2 then it will need to
support Python 2 for the forseeable future. It’ll be deployed all over the
place with Python 2 - when would the Python 2 be removed ever after 1.0? David
Murray has made substantial changes to email in Py3 -
FWIW some notes on mitmproxy and ngrep - helpful tools when intercepting and
recording HTTP traffic.
mitmproxy/mitmdump: I know doesn’t serve the same purpose as VCR but its
helpful to be able to capture and see what is going on between server and
client when Mailman tests are running.
My understanding is that VCR will capture the HTTP test request/responses and
comparison to some baseline will indicate that the API is behaving as expected.
Forgive me if I’m misunderstanding something fundamental about the VCR based
testing approach. Some questions to helop me understand:
I feel like prefacing all my questions with an apology if it’s a dumb question.
Anyway...
What’s the advantage of using VCR over a set of tests that use Kenneth Reitz
requests library to send HTTP queries to the API and have a look at the
response to see if it contains the expected HTTP
Jan 2015, at 7:37 am, Terri Oda te...@toybox.ca wrote:
On 2015-01-24, 5:08 AM, Andrew Stuart wrote:
you can look back in the archives to the huge discussion we had about
unifying the user data store..
Is there search to find that discussion or do I have to manually review all
the threads
Anyone got quick tips for dropping the entiure database and recreating it with
alembic?
I can’t find any instructions - if there are some would you mind please
pointing me to them?
thanks
as
___
Mailman-Developers mailing list
I notice that when a user is deleted, the uid record remains.
Is this because there is a bug in which the uid should be deleted but is not?
or is this intentional behaviour to prevent the uid from being recreated as a
duplicate?
My testing code does large numbers of creations and deletions of
After unlinking an address from a user, there is an address in the addresses
table that is orphaned - i.e. it does not have a linked user. This is the
expected behaviour (I think) - that’s fine, no problems at this point.
However, I can’t see a way to delete these addresses via the REST API.
for others.
Just a heads up - there may be further similar questions coming up about the
database because I’m only half way through writing my tests.
as
On 6 Feb 2015, at 3:04 pm, Barry Warsaw ba...@list.org wrote:
On Feb 05, 2015, at 10:53 AM, Andrew Stuart wrote:
I notice that when a user
Actually I meant authorization not authentication.
On 8 Feb 2015, at 12:28 am, Andrew Stuart andrew.stu...@supercoders.com.au
wrote:
TLDR - This API methods does multiple things and depends on information apart
from the URL to define its behaviour mode, making it hard to give a clear
TLDR - This API methods does multiple things and depends on information apart
from the URL to define its behaviour mode, making it hard to give a clear
authentication scope to. I wonder if it should be broken out into individual
REST API methods, each with a single purpose and a clear
After executing the curl command:
curl -X POST --data email=mailmanad...@example.org --header authorization:
Basic cmVzdGFkbWluOnJlc3RwYXNz http://localhost:8001/3.0/users
The log file adds the following:
Feb 04 11:30:05 2015 (17776) BEGIN (implicit)
Feb 04 11:30:05 2015 (17776) SELECT
$
On 2 Feb 2015, at 9:28 am, Barry Warsaw ba...@list.org wrote:
On Feb 01, 2015, at 07:23 PM, Andrew Stuart wrote:
In the commands below you can see that I start by getting a list of users, it
returns total_size: 1
How was this user created and with what email address?
I then execute a POST
Does the code of Mailman 3, Hyperkitty and Postorius do anything to address
concerns around SQL and JavaScript injections, either from inbound emails or
via the fields coming in via web interface or REST API?
thanks
___
Mailman-Developers mailing list
I might need some help to track this down……..
When a user is deleted via the REST API, there is a function that appears to be
iterating over the users addresses and unlinking them.
Is it possible that the unlinking process is somehow mutating the list of
addresses that calling function is
(you’ll need to widen your message window to see this clearly)
The following series of curl commands creates a user with an email address of
‘z...@example.org’, and then links 10 additional addresses to z...@example.org
curl -X POST --data email=z...@example.orgdisplay_name=z --header
addresses_for_deletion.append(address)
for address in addresses_for_deletion:
user_manager.delete_address(address)
user_manager.delete_user(self._user)
no_content(response)
On 8 Feb 2015, at 11:07 pm, Andrew Stuart andrew.stu...@supercoders.com.au
wrote:
I might need some help
, Andrew Stuart wrote:
I’m writing an authenticating proxy for the Mailman REST API and want to make
sure everything works as expected against real infrastructure
(Postgres/Postfix/Sqlalchemy/Falcon).
We definitely want such a proxy. It's always been our intent that the core's
REST API
Sorry I meant SAML looks similar to JWT but XML based.
On 18 Feb 2015, at 10:45 am, Dick Visser vis...@terena.org wrote:
sorry meant to sent to list, just did that now
On Wed, Feb 18, 2015 at 12:42 AM, Andrew Stuart
andrew.stu...@supercoders.com.au wrote:
Hi Dick,
If you re-post
No worries. It’s a little repetitious but doesn’t make much difference either
way.
On 19 Feb 2015, at 8:34 am, Barry Warsaw ba...@list.org wrote:
On Feb 19, 2015, at 08:10 AM, Andrew Stuart wrote:
Is there any actual benefit in those PUT methods? I can’t see what they
offer over the PATCH
Alternatively I could just ignore these methods and not put them in the proxy
although that grates against my sense of completion … :-)
as
On 19 Feb 2015, at 7:51 am, Andrew Stuart andrew.stu...@supercoders.com.au
wrote
There are several cases in the REST API where there is a PUT method that
requires all fields to be present, and also a PATCH method which is the same
except that not all fields are required.
Is there any actual benefit in those PUT methods? I can’t see what they offer
over the PATCH methods.
Does Mailman normalize dates on emails to UTC?
It seems like a good idea to me to normalise dates on emails to UTC but you
guys would know best.
What would be the pros and cons of email date normalisation to UTC? Are there
good reasons not to?
Which date field on an email is even the right
I’ve just finished (mostly) implementing most of the authentication,
authorization and permissions systems. Thought you might be interested in a
little on how it works.
To discuss this further I need to explain a few things - apologies to those who
i am teaching to suck eggs.
The auth server
, but that is really more of a relationship between a user and a list
- not a standalone resource that requires permissions - is that right?
as
On 17 Feb 2015, at 1:37 am, Barry Warsaw ba...@list.org wrote:
This looks like a reasonable analysis.
On Feb 16, 2015, at 11:39 AM, Andrew Stuart wrote
As I understand it, fqdn_listname is effectively the email address of a mailing
list. i.e. testl...@example.org
The RFC 2369 list-id is the same thing but with a dot instead of an @ symbol.
i.e. testlist.example.org
My question: is Mailman strict about accepting only email addresses in
?
as
On 17 Feb 2015, at 1:37 am, Barry Warsaw ba...@list.org wrote:
This looks like a reasonable analysis.
On Feb 16, 2015, at 11:39 AM, Andrew Stuart wrote:
To implement, it would need to be possible to define as user as being a
‘serverowner’, and also to be able to define a user as being
This command:
curl --header authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz
http://localhost:8001/3.0/addresses
Returns this data:
{entries: [{http_etag: \3045a243ea206ca6e112269f4c0ce8c4a66a92bf\,
registered_on: 2015-02-19T03:52:55.460036, display_name: Server Owner,
self_link:
[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
Hey Barry
If you are thinking of launching at Pycon, what do you think of the idea of
playing some music - you’re a guitarist right? Maybe there could be “The
Mailmen” - a Mailman band - if you can rope in some other musicians. Perhaps
the song could be a play on Elton John’s “Rocket Man”.
A
Is this defined in any way?
Is there any concept that a given Mailman user has “site admin rights”?
Or is the concept of the “site administrator” not realised in the application
and just considered to be someone with operating system level access to the
system that Mailman is running on?
config file although this just
seems to be an email address to get bounces in certain circumstances, is it
used for anything?
as
On 24 Jan 2015, at 3:13 pm, Terri Oda te...@toybox.ca wrote:
On 2015-01-23, 7:12 PM, Andrew Stuart wrote:
Is this defined in any way?
Is there any concept
:
On 2015-01-23, 9:05 PM, Andrew Stuart wrote:
you can have users with site privileges
I had a look at the data model but couldn’t see this. Would you mind please
pointing me in the direction of where user site privilege information is
stored?
I'm not sure the concept is visible in Mailman Core
compression and SSL.
Most of this is working.
as
On 22 Jan 2015, at 2:57 am, Barry Warsaw ba...@list.org wrote:
On Jan 22, 2015, at 12:02 AM, Andrew Stuart wrote:
Barry - would you like the authenticating proxy to be part of Mailman core or
a third party project?
For now, I think it should
-as-UUID is not seen
from the REST API side of things then I’ll act like that concept does not exist
and hope I’m not making things more confused around user id.
On 1 Feb 2015, at 11:31 am, Andrew Stuart andrew.stu...@supercoders.com.au
wrote:
I have read previous discussion here about format
I have read previous discussion here about format of user_id
https://mail.python.org/pipermail/mailman-developers/2014-October/024024.html
That’s fine, I understand the issues.
The question is, I am storing user ids and it’s not clear to me if I should be
storing them as INTs as returned by
, 2015, at 11:54 AM, Andrew Stuart wrote:
I’m going to store as string representation of the integer as I don’t want to
be dealing with databases or anything else that makes a distinction between
different types and lengths of integer.
That makes sense to me. Since Aurelien was okay
Successful requests to the REST API return a 2xx HTTP code to indicate success
either with or without JSON data depending on the context of the request.
At least one (I’ve not checked the othes yet) 4xx error returned from the REST
API returns a plain text error message rather than a JSON error
The user endpoint supports PUT and PATCH methods.
PATCH does a partial update of the user’s configuration
PUT does a full update of the user’s configuration
It seems that for user, the field that can be modified between these two
methods are display_name and cleartext_password
What is the
as-is and eventually turn the error text into
json, but obviously Barry you should say what you want.
as
On 11 Jan 2015, at 6:10 am, Barry Warsaw ba...@list.org wrote:
On Jan 11, 2015, at 06:06 AM, Andrew Stuart wrote:
I don’t think it’s a big deal in the short term because the plain text error
message can
Warsaw ba...@list.org wrote:
On Jan 10, 2015, at 03:42 PM, Andrew Stuart wrote:
Successful requests to the REST API return a 2xx HTTP code to indicate
success either with or without JSON data depending on the context of the
request.
At least one (I’ve not checked the othes yet) 4xx error
Attached is a first pass at a Swagger spec for the REST API.
You can find out about Swagger at http://swagger.io
The Swagger spec that I am working on is attached to this message or can be
found here: http://www.mailripper.com/api-docs.json
If you want to see the attached spec in action
The REST API is returning etags as slashed quoted.
Just wondering if this is intentional, does not seem consistent with the
behaviour of the other fields returned from the API.
i.e.
http_etag: \d6d174c76c5fbb5f8a69b648ecd3b27b53a5d27e\”,
thanks
___
I’m aware that it’s not the actual cleartext password.
From a security perspective should even salted and hashed passwords should stay
behind the API or might there be a need for something on the other side of the
API to access that field?
thanks
Yes I’d favor leave as is, and at some stage in future convert the error
messages to JSON.
On 12 Jan 2015, at 12:22 pm, Barry Warsaw ba...@list.org wrote:
On Jan 11, 2015, at 06:23 AM, Andrew Stuart wrote:
Happy to do so if you like. Would you mind pointing me in the direction of
some
a pair of
eyes to QA verify it, but maybe we can cross that bridge after I’ve finished it.
On 12 Jan 2015, at 12:19 pm, Barry Warsaw ba...@list.org wrote:
On Jan 11, 2015, at 08:51 AM, Andrew Stuart wrote:
Attached is a first pass at a Swagger spec for the REST API.
You can find out about
errr…. is this someone saying they would prefer I wasn’t on this list? I’d
rather hear directly from someone if you feel that way.
Begin forwarded message:
From:
mailman-developers-confirm+e1a7bed1fbf00db07dc7590dcbdba1e364ecc...@python.org
To: andrew.stu...@supercoders.com.au
Subject: Your
as soon as Andrew loses interest in keeping it up to date.”
;-) I was never interested in keeping it up to date in the first place but I
can’t stand doing development without API documentation, a necessary first step
to coding to the API.
I do like your idea about changes to the API not being
Should Mailman be stripping these out as part of its processing?
On 12 Jan 2015, at 2:26 pm, Mark Sapiro m...@msapiro.net wrote:
On 01/11/2015 06:27 PM, Andrew Stuart wrote:
errr…. is this someone saying they would prefer I wasn’t on this list? I’d
rather hear directly from someone if you
Sounds good to me.
On 10 Feb 2015, at 1:59 pm, Barry Warsaw ba...@list.org wrote:
On Feb 06, 2015, at 04:17 PM, Andrew Stuart wrote:
Yes it’s a tough question. I agree with leaving the uid records in the
database to prevent reuse. You are correct my test code is exercising a full
working
keep an eye out and
if I notice will report.
as
On 14 Feb 2015, at 11:59 am, Barry Warsaw ba...@list.org wrote:
On Feb 14, 2015, at 09:43 AM, Andrew Stuart wrote:
GET /addresses/{email}/memberships
GET /members
Both seem to return member id in self_link but I can’t see it elsewhere
When a user is subscribed to a list, they can be assigned a role, one of
member, owner, moderator nonmember.
The PATCH /members/{id} method does not allow changes to the role and
display_name.
I’m just wondering what the thinking is behind this - is there a reason that
role cannot be changed?
I had an idea about rounding out the Mailman permissions model, interested in
hearing thoughts on it. Obviously there has been considerable discussion on
this topic before.
Mailman already carries much of the information needed for determining user
permissions to Mailman resources. Only two
:
Andrew Stuart writes:
Is there any reason why it should not be possible to be able to
pull messages scheduled for archiving out through the REST API as
file attachments?
Oops, my previous message missed the subtlety that you do have the
message at the point in time you're considering. You still
Feb 2015, at 8:57 pm, Stephen J. Turnbull step...@xemacs.org wrote:
Andrew Stuart writes:
Why would you want to access messages scheduled for archiving”
via REST? I have trouble imagining a use case.
It would make it pretty easy to write an archiver if all I had to
do is poll via the REST
= self.create_address(email, display_name)
user = User(display_name, Preferences())
if email:
user.link(address)
return user
On 5 Feb 2015, at 7:59 am, Barry Warsaw ba...@list.org wrote:
On Feb 05, 2015, at 07:23 AM, Andrew Stuart wrote:
To get the source I do:
bzr
I can create an address that is not linked to a user by
1: creating a user with an address
2: unlinking the address from the user
Is there a more direct route to creating an address via REST?
I thought there was a POST /addresses method but I can’t seem to see it now -
maybe it was never
2015, at 1:53 pm, Barry Warsaw ba...@list.org wrote:
On Feb 08, 2015, at 12:28 AM, Andrew Stuart wrote:
TLDR - This API methods does multiple things and depends on information apart
from the URL to define its behaviour mode, making it hard to give a clear
authentication scope to. I wonder
How would user passwords work if not stored in the core?
When someone logs in currently I just ask the core if the password is valid and
off we go.
as
On 23 Mar 2015, at 8:19 am, Barry Warsaw ba...@list.org wrote:
On Mar 22, 2015, at 09:55 PM, Florian Fuchs wrote:
As for the `password`
Refer to the bottom of this email for some previous quotes from @barry on this
topic. I’ve also had off list discussions with Barry in which he has mentioned
this same topic so it seems to have some previous thought gone into it.
I’m wanting to raise the topic of “fine grained subscription
As I understand it, currently there are a few default archivers including
prototype, mhonarc and mailarchive. New archivers can be plugged in by
implementing an archiver which complies to the archiver interface. Not hard
but still requires coding skills.
Specifically if would be good if a
Fine with me.
as
On 22 Mar 2015, at 12:32 pm, Barry Warsaw ba...@list.org wrote:
I want to make some minor backward incompatible changes to the JSON
representation for pending mailing lists requests, e.g. subscription holds.
You'll see these for example in urls like:
Hi folks
I assume a great deal of thought has gone into message threading and how it
works. Is there anyone willing to share the basics with me - specifically as it
relates to Mailman and related projects?
There is of course plenty of information on google which I am researching
including the
I want to be able to turn off and on the need for moderator to approve
subscription requests.
Would someone mind please pointing out where this is configured?
thanks
as
___
Mailman-Developers mailing list
Mailman-Developers@python.org
Hi Abhishek,
If you are going to do this sort of development you will need to become
familiar with tools for observing the traffic being sent from the web browser
to the web server.
What sort of operating system are you using?
Right clicking in a browser window that you run your JavaScript
subscription requests (via REST)?
thanks
as
On 6 Mar 2015, at 8:39 am, Andrew Stuart andrew.stu...@supercoders.com.au
wrote:
I want to be able to turn off and on the need for moderator to approve
subscription requests.
Would someone mind please pointing out where this is configured
Who is who is this pic?
as
On 4 Mar 2015, at 7:09 pm, Terri Oda te...@toybox.ca wrote:
Thought you all might want this for your wall. ;)
https://www.flickr.com/photos/kushaldas/13953404515/in/set-72157644185026745
And since we're about a month out and it's probably not too late to make
understanding stands at mainly writing javascript equivalent of everything
present in _client.py(mailman client) alongwith documentation and tetsting.
What more is required to be done in this project..?
On Fri, Mar 6, 2015 at 2:38 PM, Andrew Stuart
andrew.stu...@supercoders.com.au wrote:
Hi Abhishek
Agreed Stephen.
It would be good if only configuration was required to drive the archivers even
though they are only examples/provisional/contrib whatever.
I’m hoping that projects like Hyperkitty and my server won’t need installers to
touch the Mailman source code at all to get data flowing
I wasn’t aware of MM2 topics. MM2 topics looks interesting but I agree its
implementation is cumbersome. I think somewhere in the intersection of nosy
lists, dlists, topics and fine-grained-subscription controls is an elegant way
to reduce noise and improve relevance and user experience. I’m
Dave
You seem to have an interest in Mailman being accessible.
Care to share some requirements/requests/tips/pointers for the various people
who are writing user interface code that talks to Mailman.
I’d like to take this sort of thing into account early in the process if
possible so now is a
The wiki says:
Hyperkitty is mailman's official archiver, however it would be a good idea
to add an alternative to it based on message queues, either
publish-subscribe or a fifo message queue.
Florian/Aurelien,
I’m curious to understand what would be the benefit of message queue based
There’s a bug at:
https://bugs.launchpad.net/mailman/+bug/1423756
Requesting domainowner and serverowner
thanks
On 26 Feb 2015, at 10:10 am, Barry Warsaw ba...@list.org wrote:
On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote:
I’m looking forward to being able to set and get domainowner
acceptable aliases records for the
list in question.
thanks
Andrew
On 5 Mar 2015, at 11:16 am, Andrew Stuart andrew.stu...@supercoders.com.au
wrote:
Hi Abhilash
Requesting your help - do you have some time to help me with this one please?
You seem to know a fair bit about the database
complete my test
suite.
thanks
Andrew
On 2 Mar 2015, at 7:41 am, Andrew Stuart andrew.stu...@supercoders.com.au
wrote:
After I run my tests, the Mailman database seems to get into a state in which
it is not possible to delete my test mailing list and test domain.
I figure it is something to do
After I run my tests, the Mailman database seems to get into a state in which
it is not possible to delete my test mailing list and test domain.
I figure it is something to do with the database state but I can’t see what at
this stage.
this was totally unnecessary, please correct me.
On 25 February 2015 at 07:57, Andrew Stuart
andrew.stu...@supercoders.com.au wrote:
Please disregard. Apparently there’s websites that let you search the
Internet, through which I found:
https://pythonhosted.org/mailman/src/mailman/commands/docs
path.
as
On 22 Feb 2015, at 5:05 am, Barry Warsaw ba...@list.org wrote:
On Feb 20, 2015, at 07:25 PM, Andrew Stuart wrote:
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
as
On 22 Feb 2015, at 9:36 pm, Stephen J. Turnbull step...@xemacs.org wrote:
Andrew Stuart writes:
Do you think this has to be integrated into the core for 3.0?
I'd still prefer to keep it separate for better experimentation
and testing.
the alternative for me is to go ahead with deploying
I want to inject some test messages into Mailman to test moderation functions
via the REST API.
Any ideas on a simple way to do that?
Ideally I need to be able to clear them out somehow too.
thanks
as
___
Mailman-Developers mailing list
Warsaw ba...@list.org wrote:
On Feb 22, 2015, at 11:20 AM, Andrew Stuart wrote:
there was an “application data” table:
resource_type | resource_id | private/public | key |value
”.
The question is, who do I ask for confirmation that the idea is solid and will
be merged assuming all requirements are met for code
quality/testing/documentation?
thanks
as
On 24 Mar 2015, at 4:27 pm, Terri Oda te...@toybox.ca wrote:
On 2015-03-23 8:38 PM, Andrew Stuart wrote:
I haven’t
@barry - would you mind confirming please you’re OK with this please?
I’m going to implement some very simplistic, working, example archivers. As
discussed with Stephen, although functional, these will be “working examples”,
much like prototype.py is currently, and won’t be presented as
@barry, @stephen, @terri
I know this is a wall of text (sorry) but if you have time I’d be interested
to hear your thoughts as Dynamic Sublists are in the GSOC projects list for
this year.
as
On 20 Mar 2015, at 9:53 am, Andrew Stuart andrew.stu...@supercoders.com.au
wrote:
Refer
, Andrew Stuart wrote:
The main thing I’m looking for is whether there is an authorisation concept
that operates at a higher level than the list.
No, there isn't[*].
I wonder is there the concept of some sort of “special” mailing list that is
different or hidden or privileged in some way
Aurelien I’d be interested to hear your thoughts on this topic.
as
On 22 Mar 2015, at 10:13 am, Andrew Stuart andrew.stu...@supercoders.com.au
wrote:
As I understand it, currently there are a few default archivers including
prototype, mhonarc and mailarchive. New archivers can be plugged
1 - 100 of 121 matches
Mail list logo
