SoC mid-terms and your first alpha release
Those of you paying attention to the SoC timeline will note that mid-terms are July 7, 2008. At that time, two things will happen:
- Both students and mentors will be required to fill out a small survey from Google. Monitor the mailing list for details.
- Students will be required to release an initial alpha version of their projects that the community can play around with and test. Extra bonus points for having a public demo site that people can click and try!
"But webchick!," I hear you cry, "It's only half way through SoC! My project isn't done yet! How can I possibly release an alpha version?!" It's quite easy, actually:
- Get whatever aspect of your project you're currently working on to the point where it's basically usable by normal humans and won't explode peoples' test sites.
- Commit all of your code to CVS (you should be committing your code at least daily, anyway, as a best practice... preferably each time you finish a little chunk of work).
- Write a couple sentences of documentation in README.txt that outline how to use what you have so far, making it clear what isn't done yet and is still "off limits".
- Follow the instructions under http://drupal.org/handbook/cvs/quickstart#release-tag for creating an "Official" release.
This will allow us to make a SoC mid-term post to get you guys some press, and get some end-users testing out the functionality you've built out so far. Taking this feedback into consideration early will help your project become that much stronger in the long run. Additionally, it'll also help motivate you to make sure you have code actually committed by midterms. ;)
Please ask in #drupal or to your mentors if CVS is giving you any trouble. Looking forward to trying out your hard work! :D
PS: Tell us some stuff at the introductions post if you haven't already, too. :)
sorry for no commits
I do make commits at least daily. . . but just on my local machine. I have a git repository. I didn't realize I should be making commits to Drupal as well. I guess it would be easier for others to help me if they could see my code. . .
Kyle Mathews
Yep :)
Btw, thanks for your many detailed status reports; you're not one of the projects I'm worried about, but it's still great if you commit stuff periodically to Drupal CVS because then others can read what you're doing and offer advice.
Me too
I've been doing the exact same thing. I'll try to get myself to commit to drupal.org more than once a week from now on.
Oh btw, EXTRA bonus points
Extra points if you have a public demo server up so that people can try your project without having to install anything. You will get far more testers that way. But if you go this route, your demo should be running the alpha release that you create for mid-terms. ;)
Also, don't spend so much time on this that it takes away from actually getting your project /done/. :D
yAy Here I fall in
My test server is up with latest code :)
http://tut2tech.com/sb2/
for making test OAuth calls end points are at user page
and you can also look for changes in Services API to see how it is gonna work with OAuth protocol now
by making test calls with generated OAuth tokens
to make oauth tokens use
http://tut2tech.com/sb2/?q=admin/oauth/services
OR http://term.ie/oauth/example/client.php
this is a rough URL form will edit things in it by tomorrow :P So will update here as well
I haven't made any commits myself for code
But will make in 1-2 days as I just got OAuth module's commit access
sumit kataria
www.sumitk.net
Unfortunately,
Unfortunately, we can't see the source code behind that because it isn't in CVS! Please commit all your code to CVS, like, as soon as you're reading this. We need to see the code you're producing, to make sure that the code itself is on track.
code is coming very soon
I will upload code very soon
you can check issue queues for my earlier patches and code
http://drupal.org/node/238814
will upload to cvs and queue in few hrs.
sumit kataria
www.sumitk.net