The phpEdu project page has been sitting dormant since it was created last year. There is no code is CVS. Today, the owner announced there is a dev version and the project page was updated to include an offsite download link. Is this against policy?

Comments

greggles’s picture

Status: Active » Needs review

I believe that's the case.

I modified the page and left this issue in the revision log and submitted #329483: move code to drupal cvs

Let's wait a bit with this issue to ensure that the procedure was communicated.

dakala’s picture

If indeed there was a breach of policy, I do apologise but it wasn't deliberate. In actual fact, there has been a number of news updates with regards to work on phpEdu and a few people have raised questions on it.

greggles’s picture

From a private mail:

Anyway, I'm at a loss with regards to the use of CVS for this project as I
include Drupal 6 and other required contrib modules in the package - for
compatibility and ease of downloads - in addition to phpEdu-specific
modules of course.

Any guidelines (or referral to relevant pages on d.o) would be very much
appreciated.

You should commit any pieces which do not duplicate existing modules. For example, if your project is an installation profile and a single module then you would commit the profile, and the profile specific module, but leave the modules required by the profile out of your CVS tree.

I don't know of a single good resource on the topic, but I think http://drupal.org/node/314492 and http://drupal.org/handbook/cvs are about the closest things we've got.

dakala’s picture

Thanks, greggles. I'll commit only phpedu-specific modules and think of how to manage dependencies and compatibility. Making this a profile project wouldn't be very satisfactory either but worth considering. These are the kinds of issues I'm rather not clear on and not CVS use.

silverwing’s picture

Status: Needs review » Closed (won't fix)

Wont Fix-ing this - there is currently a -beta4 version for D6 from May 2009 available.