search

dominickm / jupiter_broadcasting_mobile_community

The Jupiter Broadcasting community project.
Other
100 stars 17 forks source link

Project Status #15

Closed ghost closed 11 years ago

ghost commented 11 years ago

OK so is this project dead?

The pull request has just sat there. Whats the news?

ograycode commented 11 years ago

I would say so. I purpose either Dominick give admin rights to a few people so they can administer it, or we fork and do the same so the project can move along. I would be willing to fork and move along, and admin over it with some others.

Oh distributed version control.

dominickm commented 11 years ago

@ograycode I'll pass you admin. Don't have enough time actually run the project.

@Techfix I thought I merged in your pull request let me check.

dominickm commented 11 years ago

@Techfix Ok merged in sorry about that.

@ograycode you should now be in the admin group.

ghost commented 11 years ago

Cool, I haven't done any work since I was waiting for the pull request to go through so I could update my local repository with the changes. Now I can continue to work on the project. Do I have admin rights? I have got lot better at GIT since we started.

Either way the pull requests need to be dealt with quickly.

ShaneQful commented 11 years ago

Yay, I have some work in my local repo that I'll commit up the next few days :) Also if anyone who likes/uses java wants to help out with the current jb android app or god forbid the JavaME app. The repos are here and here respectively.

dominickm commented 11 years ago

I'm glad your happy. I am going to try to be more involved in a few works, but I have also given others elevated permissions and may do so for one or two more.

I look forward to your code!

-- via Code Journal

ZefQ commented 11 years ago

I just found coder radio, a bit late I know. Anyway I would love to help out with this project if help is needed.

ghost commented 11 years ago

@ZefQ its never too late - help is always needed. dominickm is the one who started and runs the project/repository. However I would like take the time to welcome you. I noticed you haven't forked the repository which is always a good start. It may be most helpful to read through the issues if you haven't already as that is where the discussion is.

The project uses:

Our intention is for the application to work on both Google Android and Appple iOS Devices.

We have just started so please feel free to make contributions and so on. Please remember that this is an learning experience for some of us (including myself) and an opportunity to be part of a development project with the intention to release the app in respective app stores.

We have a code style based on the Google guide: http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml

Please ensure that you use a jslint tool for the JavaScript before submission to ensure code quality.

May I recommend that you at first look at the "Start and maintain a requirements/spec file" issue (https://github.com/dominickm/jupiter_broadcasting_mobile_community/issues/3) which contains the main discussion on the features of this app.

Happy Coding!!!

ZefQ commented 11 years ago

Thank you. Yeah i read through everything yesterday to find out what the project aims for, which function to prioritize for first release, what was already done and so on, I must say that it is a bit vague on which functions to prioritize. Might i suggest a list of small tasks with the priority of the task and a note that say if its done, someone working or the task or not.

I think that that might help people to decide what to start working on (like me =) ). One might use a simple text-file, the issue function here or maybe a project/task-manager kind of like basecamp. basecamp is not free but there are alternatives. for example i found this a couple of days ago http://taskant.com/ that allows unlited users for free accounts but i would guess that there is others that are better. Anyway just a thought

ghost commented 11 years ago

Good idea. The way we seem to be working is that you simply work on what you can or what you want to do. For instance we know that the app should be able to get the RSS/XML feeds that JB uses and play the content both audio and visual. So far for example @ograycode submitted a way to get the latest feed items and I created the UX. @lukeab and others have helped to establish the policies including how we should commit.

So it really depends on what you want to work on. There is no restrictions or limits, so if you have an idea for the application or a way to improve something; you just need to commit it to your fork then create a pull request. As long as you adhere the the style guide and that it doesn't break anything it is likely that it will be added.

You can find all this information regarding what we have done so far via the GitHub->Code->Commits: https://github.com/dominickm/jupiter_broadcasting_mobile_community/commits/master

As for a team To Do list. We could simply create a issue called to do and then add to it. I don't know how it would work out in practice.

@dominickm should we create a todo list? what do you think?

ShaneQful commented 11 years ago

I agree with @Techfix the easiest way to do a todo list or split up features is just use github issues.