[swift-evolution] Pitch: (Almost) std libs
dturnbull at gmail.com
Fri Jan 29 18:42:58 CST 2016
The org isn't private so I'm not sure what you're trying to join on GitHub
but you can contact me off-list to figure it out.
The core team is very small and super busy. You're asking them to take on
more administrative work and responsibility. If they were interested in
doing so at this time I'm sure someone would have joined the conversation.
I'm trying a different approach. Maybe it won't get very far because I'm
not influential enough. But if I can herd enough code to demonstrate the
potential of this idea, it's a lot easier to ask Apple to take on extra
Ideas like this are substantially different from language changes. They can
alter the evolution of Swift but you can't put it in a typical proposal.
Think of my GitHub experiment as a proposal, not an implementation.
On Fri, Jan 29, 2016 at 9:31 AM, Tino Heth <2th at gmx.de> wrote:
> I was thinking about the requirements to make this happen. It only needs
> someone to do the initial organization. So I created a GitHub organization
> and put up a couple projects. The Matrix4 project is feature-complete. The
> Complex project is just a foothold.
> Now we need more projects. The readme in the contrib project has
> information about getting your project added.
> I fear it won't be that simple…
> First problem: "Hey github, where can I request team membership??"
> I just starred the contrib repo, and I guess you can use this information
> to bring me into that team… but it should be more straightforward to join.
> Or wait, maybe I'm to quick here: Should it be easy to join at all?
> The second problem is most likely the real showstopper:
> Establishing a real standard requires influence, and that is hard to earn…
> It is possible someone else starts a project with the same goal next week,
> and maybe someone already did it last year, and I just don't know about
> that "standard".
> Although no absolute requirement, chances for success would be
> significantly better if the project was managed (or at least supported) by
> an accepted authority — and taking into account that it is desirable that
> ultimately its results are shipped with Swift itself, the preferred choice
> for a manager is someone working in the Core Team (or, more general: At
> I don't know how successful ResearchKit is right now, but I guess it could
> act as a prototype.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution