On 21-Oct-2017 Ben Finney Wrote:
>In its early days, can I convince you to move the project away from
>the proprietary GitHub silo?
Absolutely, and I see these as legitimate concerns. I had quite a hard
time getting things like GitHub webhooks to post to the channel and
I am not a fan of GitHub already. I posted to GitHub and SourceForge
just to get it out there and have a place to keep things. I have no
experience with these things and would prefer someone who did take
lead on this.
I am not familiar with any of these tools so I have no preference.
I was just trying to find a place to outline the ideas well enough to
allow people to wrap their minds around a vision I developed over 15
years of using and supporting Debian and seeing various issues.
As you can see the wiki isn't all that detailed just an attempt to break
things down so people can flesh out the specifics of an API.. and we
have no actual code yet this first week has just been publicizing the
idea, garnering support for development and noodling design ideas.
I'm totally open on everything right now the only things I'm somewhat firm
on is that this needs to be done, and that it should include components
that integrate directly into the OS, wrap our existing support resources
without people who already know how they work having to change the way
they do things, and that Python should be the language for development
simply because not only does it seem most well suited to the task for
making development go smoothly.
I can either take a similarly inexperienced crack at moving/recreating the
project elsewhere or someone can just take lead and create a new home
themselves and I can update the existing information pointing to the
new location. It really doesn't matter to me. I have little more than a vision,
experience with using and supporting Debian, and a working but rather
inexperienced understanding of Python. I will either have to learn as I go
or will only be slowing the project down if I remain the leader of this show.