Comments (10)
from ayo.
Hey @kulshekhar, sorry you can't create any issues right now. No-one apart from org members can, but tomorrow, everyone will be able to post issues again.
I've gone through those issues but couldn't get a clear picture. It would be hard to provide any meaningful input without knowing the technical goals of the project.
Absolutely, I agree. There is no centralisation of information about what is currently happening in Node core, and I'm not the person to write it. But, speaking for myself, I am interested in Ayo because I am personally unhappy with the leadership of Node core, and want to see if someone else can do better.
As the fork has existed for (less than) a day, there really isn't anything to share. I know that's frustrating, but that's where we're at right now.
Right now, what I'm most interested in is thoughts on #2. Obviously, you can't comment right now (sorry, nor can anyone) but tomorrow I'd love to hear any thoughts you have on how Node could be governed differently. Even if Ayo doesn't become a thing, I think it's a valuable discussion to have, because we can suggest these ideas to Node and see what they think.
<3
from ayo.
Right now, what I'm most interested in is thoughts on #2. Obviously, you can't comment right now (sorry, nor can anyone) but tomorrow I'd love to hear any thoughts you have on how Node could be governed differently. Even if Ayo doesn't become a thing, I think it's a valuable discussion to have, because we can suggest these ideas to Node and see what they think.
Understandable, but I can't really comment without knowing what the problem is exactly. The Node.js project has already had a major fork in io.js and I really liked the results at the time.
It's only natural as things settled down that new problems emerge, but I truthfully do not follow the community close enough to know. I guess that would make me a user of Node.js rather than a contributor, and as such, some of the more esoteric issues with governance or community are things I am not really aware of too much.
But I could get behind io.js back in the day because @mikeal and others did a great job of communicating it all to someone like me, who is not involved in the day-to-day stuff and just wants to write great shit with Node.js.
tl;dr +1 on wanting a mission statement on the fork!
from ayo.
There is now a PR, #15, with a draft of the values for this project.
from ayo.
Is there a document or an authoritative post that outlines the reasons behind Ayo existing and lists the goals of this project?
Not yet. This project was forked yesterday.
Take a look at the other (currently 2) issues in the repository, we'd love input!
from ayo.
Bring fiber in core code like fibjs did or merge to it?
from ayo.
@yuu2lee4 maybe you could open a separate issue for that?
from ayo.
@mtimofiiv Would love it if you could review #15, which is a "mission statement" for this project.
from ayo.
But I could get behind io.js back in the day because @mikeal and others did a great job of communicating it all to someone like me, who is not involved in the day-to-day stuff and just wants to write great shit with Node.js.
I'd like to point out briefly that back in the day we (members of io.js) actually had considerable trouble describing what differentiated ourselves from Node. We ended up just going with "Node plus ES6!" but it was really much more than that. 😉
from ayo.
I think we've answered it well, in the form of our values document.
from ayo.
Related Issues (20)
- fs.copyDirectory HOT 1
- Ayo.js Core Team meeting 2017-10-13 HOT 3
- where are the missing devs HOT 3
- Discord invite has expired HOT 3
- what is ayo? HOT 7
- what is the rationale for this project.. HOT 2
- Compiling for Android
- COC violates Code of Conduct HOT 1
- ded projekt? HOT 4
- Summary of resolved issues? HOT 2
- Project status?
- Update references to default branch to `latest` HOT 1
- Define clear goals/motivations of the Ayo.js project HOT 11
- Is ongoing interoperability with Node.js a requirement for Ayo? HOT 11
- Reconsidering some semver-major changes from upstream? HOT 9
- Sub-team governance issue HOT 11
- Windows builds HOT 2
- First core team meeting! HOT 27
- Create an initial release HOT 3
- contributing.md changes that we may want to backport HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ayo.