[Soap-Python] soaplib's new maintainer

[Brad Allen]

On Mon, Nov 22, 2010 at 8:09 PM, Burak Arslan
<burak.arslan at arskom.com.tr> wrote:
>  On 11/23/10 03:42, Brad Allen wrote:
>> We've gotten a bit delayed on the beta release; the main holdup right
>> now is getting the GitHub issues migrated over to the new GitHub repo.
>> We wanted the "official" repo to be owned by an organization instead
>> of an individual; the name we came up with is slightly silly but
>> should serve the purpose.
>>
>> If you want to become a core contributor, you'll be joining the
>> "soapapistas" group on Github. :-)  If anyone comes up with a better
>> name, let me know.
>
> hi brad,
>
> i'm afraid i'm a bit disappointed in this announcement.
>
> i don't see why you'd need to have a new organization, especially when
> it's so much of a hassle. soaplib was, before migration to
> arskom/soaplib organization, watched by more than 50 people. we're yet
> to reach that number. and that migration happened because 1) it was
> jkp's personal repo and not a proper organization, 2) i had to rewrite
> git history to deal with previous screw-ups, so we needed a new repo anyway.
>
> so please explain why you absolutely need to migrate to a new
> organization. the way i see it, it brings nothing positive to the table
> and hinders what little traction the project has.
>
> that said, i own both github.com/rpclib and github.com/soaplib
> organizations. so if you're adamant on migration, can come up with a
> proper excuse, and you're after a less ridiculous name, i can grant you
> rights on those addresses.

github.com/soaplib seems like a good choice, though that gives us a
lot of urls that contain "soaplib/soaplib" which seems awkward.
"soapapista" was supposed to be a play on sopapilla + Pythonista, but
I guess it does come off as ridiculous. Does anyone have a better
suggestion for an organization name? Chris suggested "soaplibbers"...

I would strongly prefer for soaplib to exist under a GitHub
organization rather than an individual, for some of the reasons listed
here:

    https://github.com/blog/674-introducing-organizations

The most important is multiple administrators; I need the ability
delegate access privileges to others. Also, currently you are the only
owner of arksom/soaplib, and you will be inaccessible in the near
future. If we need administrative capabilities, such as adding other
core contributors, we'll be stuck.

Additionally, I expect to see multiple related repos tied to the
soaplib project, which can fall under the same organization. For
example, we may decide that support for particular servers such as
Zope, CherryPy, Twisted, etc., be put into separate packages outside
soaplib. Another possibility is spinning off soaplib.model because
it's useful outside a SOAP context. We're not doing that for now
because we want to get out the release ASAP, and that kind of decision
needs to be vetted with the community.

Another advantage of using a GitHub organization: the next change of
maintainers will have a smooth transition path and won't have to worry
about this.

I think the number of GitHub followers can be regenerated at the new
repo location. Good docs, beautiful APIs, robust functionality,
thorough test coverage, and an inclusive community process will do
wonders for adoption.

We do need to figure out how to migrate the issues, though. I've
spotted Github support tickets where this has been done by Github
administrators, so we're planning to seek support on that tomorrow.