-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Developer Feature Wishlist
Below is a curated feature wishlist of things the core team love to have some help with for the Diaspora project.
If you choose one these features, a core team member will help you get your pull request merged. It is a fast track way to get involved with the Diaspora* codebase.
Community developers are more than welcome to dive in and work on these at any time, please contact the mailing list about any of the items listed below that you'd like to help with. Also, don't be afraid to join in and help out other developers with existing projects
"In Development" items will be linked with a thread to Google groups, so as to encourage collaboration and avoid duplicating effort.
AppConfig is the current class that handles loading Diaspora’s settings from application.yml. It has grown into a bit of beast, worring about bootstate, data munging, and a few related helpers. The time to clean it up is now! We should move all logic out of AppConfig, and let it just be a SettingsLogic class. Then, we should access everything via EnviromentConfiguration, delegating applicable keys and to AppConfig.
Many projects have a script which makes it trivial to get a development enviroment running. It would be awesome to have a script that bootstraped the minimum enviroment needed to run the entire test suite. That way, it would be easy for new developers to clone the repo, run the script, and run the tests, all in one swoop. As a start, which should make this process seamless for the following three enviroments(then we can work on something more general. 5) mac os x 7) ubuntu development 8) virtual Box Setup(we can host the final box)
See these(https://github.com/diaspora/diaspora/blob/master/features/post_viewer.feature)? Now see how much worse this is?( https://github.com/diaspora/diaspora/blob/master/features/edits_profile.feature). A lot of our cukes are messy, it'd be great if someone with a great sense of code clarity were to step up to the plate and refactor some of the features. If you want to go the extra mile, work with dennis and Identify tests that would be better in jasmine, or unit tests to shave some time off the suite as well.
There are a bunch of things a seasoned Rails dev would want to do here. Utilize more rescue_froms to reduce branching, breaking really big actions into objects that are delegated to, to just improving and backfilling tests. This is not the most glamorous of things on this list, but it would be much appreciated.
We already have rails admin running. It might still need some configuration tweaking. We could make a couple of static pages, and move some of our custom functionality to the rails_admin side of things. Other ideas are basic webfingering other pod dev tools, showing the list of connected pods, and adding links to things like resque status etc etc.
7) Pod Customization (In Progress).
We're discussing how to turn some variables into strings to make pod customization easier for podmins without needing to fork from the main codebase. It's a great starting point for figuring out how further to customize a pod.
needs to upgrade carrier-wave, and include a hack in the carrierwave wiki.
Ask Max for more info.
After a user has signed up, email them with helpful information.
Adding a tag under the /followed_tags should be using JavaScript to do so. It would be cool to have that feature. Also, considering the fact that deleting a tag is already using one, we think it should be in symmetry.
There's a lot of unused images in there that we don't need, so it kind of makes for a waste of space.
Make Carrier-Wave upload to a /tmp directory for tests, and clean up when done.
Currently, our mobile site is relatively simplistic, and could use some tweaking to be made more accessible. A discussion needs to happen to figure out what new features would be desirable.
14) Add Tests to This Pull Request
This was contributed to us by a user. It's a relatively simple fix, but the contributor was unable to write tests for it. Let's help this person out and make sure that we can get it merged in!
Please document the existing code and also consider documenting your code as much as you can when you send us a pull request. It helps others who fork the repository to understand and work on it.