Skip to main content ↑ ↓
Topic: Relevant project links (Read 8240 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Relevant project links

This thread is here to help me (oops), and we all, to know the relevant documentation on the project available so far.
All of them need your input and help, and welcome your contributions.

Roadmap:
Estimated targets (personal and rough):
- 1.0 beta - March 2013
- 1.0 stable - Autumn/winter 2013
@emanuele's update:
- 1.0 stable - first quarter 2014.
@emanuele's 2nd update:
- 1.0 stable - first half 2014.

Development:
Documentation:
Contributing to the wiki is easy: just like any other wiki, it allows free edition of pages. A lot of user documentation can be "inherited" from SMF, since the first version is almost fully compatible with it.
The changes from SMF should probably be documented separately. Thoughts?

Special notes for developers:
https://github.com/elkarte/Elkarte/wiki/Architecture
At the bug tracker, you can find a list of (hopefully) easy bugs that can help introduce to he ElkArte development. Feel free to pick one or more and fix it. ;D

Bug/enhancements Tracker:
https://github.com/elkarte/Elkarte/issues

On external tools/functionality:
https://github.com/elkarte/Elkarte/issues/14

QA testing:
http://www.elkarte.net/index.php?topic=824.0

Question that has been asked:
- What about addons and themes, will we make a central repository or database/site, or not?

My (own) take on it:
- not make a site, but we can and will (probably) initiate two repositories on github, for the addons and for the themes from the community. Once we do, we'll document how to publish addons and themes, to it. It's up to you, the community.
- package servers are a feature of Elk, which has been underused (read: not used) in another world. We encourage you to create your own package server, with or without a site, as you wish, and publish your addons on it. You can always notify people here, of your package server, and they can add it to their installation.
Last Edit: May 30, 2014, 12:00:56 am by emanuele
The best moment for testing your PR is right after you merge it. Can't miss with that one.

Re: Relevant project links

Reply #1 –

Repo for themes, and another for mods, sounds cool for now. Can do a site later if it becomes desirable, but a repo is a good starting point.
Master of Expletives: Now with improved family f@&king friendliness! :D

Sources code: making easy front end changes difficult since 1873. :P

Re: Relevant project links

Reply #2 –

Small bumpy for your information.

I have updated more comprehensively (I hope), the roadmap on Github, and I've referenced more of the targets and functionalities that we have achieved or are in progress.
As you can see in the top description of the roadmap-issue: I use direct references to the pull requests with completed features, to the branches with work-in-progress, to the other Github issues tracking what is in consideration, and respectively discussions here, on the forum, where they're relevant.

The targets aren't so many, but they're very important, and the core developers have been working on them since 2.0/2.1. But my intention on the roadmap is for everyone to find it a resource where you can track progress, you can find what is missing and needed, you can participate to it.
The next milestone, 1.0 beta, is important, to tell the world what Elk is, and it means feature-freeze. So if you have goals you want to achieve for 1.0, don't forget this last bit: add/propose/make it for beta.

Also, as I noted in another discussion, I have enabled the milestone tracker on Github:
https://github.com/elkarte/Elkarte/issues/milestones
I am keeping it up-to-date. (except when I'm not :) ).
For everyone to see a quick view. Do note that it's very approximate, in case it's not obvious. :)

If you can improve the presentation of the roadmap, if it doesn't give enough information or hands-on assistance for your wants from Elk, please go ahead and let us know how to improve it. Or make a wiki, a topic, or whatever else you see more suitable.
Last Edit: February 24, 2013, 11:28:25 pm by TestMonkey
The best moment for testing your PR is right after you merge it. Can't miss with that one.

Re: Relevant project links

Reply #3 –

 emanuele feels he has to finish those 3/4/5 things left pending here and there... O:-)

 emanuele whistles innocently
Bugs creator.
Features destroyer.
Template killer.

Re: Relevant project links

Reply #4 –

Virtual bump. :P

Beta has been release, so I updated the first message with an ideal release period of first quarter 2014, should be doable...unless I'm wrong of course. O:-)
Bugs creator.
Features destroyer.
Template killer.

Re: Relevant project links

Reply #5 –

Updated a bit the first message with some more info.
I've been suggested to provide a list of "easy" stuff that may help introduce to Elk development, and for the moment, this is the best I can do:
https://github.com/elkarte/Elkarte/issues?direction=desc&labels=easy&milestone=4&page=4&sort=created&state=open
I created a new label at github tracker and attached it to some bug/feature requests, those that look easy to me (but easy is subjective, so I can't be 100% sure).
Bugs creator.
Features destroyer.
Template killer.

Re: Relevant project links

Reply #7 –

 emanuele is ahead of himself :P
Bugs creator.
Features destroyer.
Template killer.