New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discussion] Improving our development process #4396
Comments
I'd like to point out that contributing under the current regime is pretty rewarding - the community we have hear is nice, helpful and in general pretty awesome. I personally am having a lot of fun doing it. Telling friends about it, I keep hearing one thing though: "Why would I code for free for a company?". I'm very much aware of how this statement is invalid and requires a "wait, that's not the point [...]", but we might be able to attract more people by making it more obvious that Ghost isn't just an open code base, but truly MIT OSS. Without having a decent overarching solution, the fact that ghost.org doesn't have a link (I could find) to ghost.org/download might be one of the contributing factors. |
I try to use the |
|
When I started to look into Ghost for the first time the other day I found myself going back and forth between the development and business sides by hopping through links that at times seemed fragmented and overwhelmed and not sure at first If the information was for developers or end users. For example, I think it would be great to see Ghost divided into two domains of information: one for developers and one for end users/customers. For example,
It might help with getting new contributions if new developers have easy access to information by accessing one domain that’s focused for them. The public roadmap on Trello looks great! Just my 2 cents. 👍 p.s. I do hope to contribute something (whether it’ll be testing or trying out beginner’s issue) once I’m more familiar with the inner workings of Ghost and its dependencies. 😄 |
Personally I wouldn't move IRC to Slack. While WordPress and #nomads have done it, and both have 600+ users in there, it's unmanageable. Slack is awesome for small teams, but for large groups it becomes VERY difficult. I muted notifications from the WP and nomads teams, which just means I don't even check them. Also, IRC is easier for users to hop in if they have a question. |
Thanks @javorszky. I haven't got experience in big groups only groups of ±10 so I can't argue with you there. :) Nice thought, but if it's not feasible then it's one of those things. I guess my comment was in part driven by my lack of personal IRC adoption, Guess I just haven't used it enough. |
For anyone struggling to find an IRC client: www.irccloud.com Just... do that. It replaced textual overnight for me. :) |
:-) |
ref TryGhost#4396 - adds a TLDR, updates links throughout & improves language
Very nice discussion. 👍 |
In terms of process I have often worked within variations of agile. I have used Jira as an issue tracking tool many times and one of the great things about it is that it really easy to see tasks that are in progress. I have been trying to get started/involved and managed to find out about the beginner label being used through reading the getting started guide but where I have spent a lot of time confused now is knowing if an issue has been started on by someone. Perhaps a rule that you must assign the issue to yourself once you begin on it is in store to clearly show progress? An example of this would be this issue #4596 |
The problem with assigning people is, they have to be a member of the On Wed, Jan 28, 2015 at 6:15 PM, Raúl Felix Carrizo <
|
Ohhh right... of course. It then becomes a management issue for someone then. |
I'm gonna close this now as feedback has dried up. I'm working on cleaning up the issue list, using the tags We have since moved our community from IRC to slack and there you can find both a #dev channel for discussing core development issues, including getting help with contributing and also a #help channel for general Ghost issues. There's also an #i18n channel for discussing that project and a #themes channel for sharing themes and talking about theme development. I'm always interested in feedback on how we can improve the contributor process so if anyone has ideas please post here or come chat in slack! |
Lately, we've been trying out new things with our development process in order to get a bit more fluid (agile) and move towards releasing little-and-often instead of dropping great big releases every few months. Some of this has gone really well (we're releasing more stuff faster) and some of it hasn't necessarily (I don't feel like the process is particularly clear). So I'd like to get some feedback on ideas on how to get better at doing what we do.
I have the following goals:
To aid the conversation, below is a little bit of an overview of the way we work:
Backlog
column is a list of things we want to do one day (for v1.0),Next
is for things that are ready to work on and we want to get into a release, andIn Progress
is for things which are actively being worked on.Current
which contains the 'top 10' priority items for the next release,Next
which contains everything else that is ready to be picked up and worked on, andFuture
which contains other tasks we're tracking but that are blocked on something else.Some ideas to get us started:
I'm very, VERY interested to hear feedback and new ideas. This is going to be pretty much all personal opinion, so in the interest of keeping the discussion positive, productive and awesome, please try to qualify your ideas and concerns by telling us about your workflow and how the processes do or don't fit in.
The text was updated successfully, but these errors were encountered: