Make it public

[sindresorhus]

I see no reason for this repo to be private. Progress is slow and making it public could attract more contributors. Any objections?

[henvic]

Not mine. It should be public.

It's open source and the worse that can happen is a pull request not be merged or (improbably) a hostile fork, after all.

[arthurvr]

👍 Why not?

[ruyadorno]

👍 @sindresorhus @henvic agreed and agreed

@arthurvr originally, the idea was to have at least a working version before opening it to the public but as you can see progress has slowed down to almost a halt after end-2014.

I would wait for feedback from @stefanbuck before taking any decision though, he has been the most active contributor lately 😊

I believe it might even motivate us more to find the time to finish the remaining tasks for the first beta milestone 😄 or at least I hope so

[addyosmani]

👍 for opening it up if feasible

[stefanbuck]

I wouldn't do that ... not now for the following reason. The App doesn't work, even the basic stuff like promoting. Everyone would be disappointed right after the first clicks. Of course, many potential contributes could fix issues and build new features very fast.

@ruyadorno and I want to build an application which is worthy to use. The first touch with the app should be a "wow" moment and make the user smile.

My suggestion. On Sunday (I'm unfortunately off the whole weekend) I will create issues for the remaining task. @ruyadorno and I will prioritise them and start working on them. We will not trying to cover all the issues, only the important ones.

After that I'm more than happy to make it public!

[ruyadorno]

@stefanbuck yeah, those are good points

Even though I really hope to get some "wow" from the initial users, reality is that the first batch of users will probably be other hackers and enthusiasts like us, hopefully some of them might even be inclined to jump in and help with development once they find about it.

I'd suggest that we set a deadline to try to get it at least in a functional (not-disappointing) state before opening the repo to the public. Thoughts?

[stefanbuck]

reality is that the first batch of users will probably be other hackers and enthusiasts like us, hopefully some of them might even be inclined to jump in and help with development once they find about it.

Exactly 😉

To have a deadline is a good idea. What about 27. June? Maybe it's a little bit tight, but I'm in vacation from 28. – 5. July (with limited internet access) and after that I'm in the UK for one week.

[stefanbuck]

@ruyadorno created some issues, YEAH!!! Feel free to add more stuff and prioritising them.
– Thanks

https://github.com/yeoman/yeoman-app/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+author%3Astefanbuck+created%3A2015-06-12

[stefanbuck]

Hey, I moved #27, #30 and #34 to milestone v1.0.0 beta, because they are not relevant for our current mission. So now, there is only one thing to do before making this repository public. @ruyadorno could you please take a look on #16?

Thank you

[stefanbuck]

I'm back from my vacation and unfortunately the repository is still private. What's happening @ruyadorno? Are you busy with other stuff? What is your plan and how can I support you?

[ruyadorno]

hi Stefan,

Sorry but I'm the one on vacation now, too much stuff happening at once here.

There was only 1 issue left from the "curtains up" milestone, the loading/spinner thing. It only needs the correct events to be wired into the flux structure and add some nice graphics like the ones Sindre suggested on the linked issue.

On Jul 5, 2015, at 4:48 PM, Stefan Buck [email protected] wrote:

I'm back from my vacation and unfortunately the repository is still private. What's happening @ruyadorno? Are you busy with other stuff? What is your plan and how can I support you?

—
Reply to this email directly or view it on GitHub.

[stefanbuck]

Alright, will take a look on it. Should we wait with publishing until you are back?

[ruyadorno]

ok, we addressed the loading issue for now and I officially ask for the repo to be made public 👍

[sindresorhus]

Done :)