The Forge website is migrating. Last week the first big step was taken when all of the Forge backend processes and the front end administration pages were moved. Almost everything is now controlled in the wiki interface. This is the first major step in our transition.
Roadmap Quote:
"Novell now plans to improve the current Forge UI and update the Forge website to a new look. The previous Forge website, as you know it, will no longer be available. Most of the functionality that was available in Forge will be moved to the new developer wiki pages. In other words, the framework that connects all of the Forge services will now be the wiki instead of the forge website."
Our next major step will be to redirect the rest of the current forge website to the developer wiki. If you are a project admin, please take a little time and edit your project page in the wiki so that it looks the way you want it to look. We are planning on making this next step in the middle of May, so please edit your wiki page by then. Below are a few projects that have started to take advantage of the freedom that the wiki gives them to promote and report their project in their own way.
If you would like a little bit of transition help please take a look at Help for forge users. If you discover something useful please add it to the list of suggestions on this page. We will also continue to add information as we see difficult transition points.
If you have questions or would like to be informed of changes as they happen please subscribe the the forge-dev mailing list.
A Forge/Road Map has been created to show the direction that forge is going to be taking over the next few months. Please take a look and give us any feedback you may have.
We have redone how file releases work for Forge projects. Here is a summary of the changes:
1. Files are organized into directories instead of a strict package/release structure.
2. Files and file metadata are read directly from the file system instead of the database.
3. Administration is done inline instead of in a separate Admin section.
4. You can now replace existing files.
5. File monitoring has been removed.
6. File download statistics are temporarily disabled. They are still being collected, just not shown.
7. We no longer store 'notes', 'changes', or 'dependencies' as part of a release in our database. Instead, please include README, CHANGES, or other files with your file releases to deliver this type of information.
We think these changes will be helpful to everyone using this site. If you have ideas or problems please let us know.
We have updated the look of the project Summary pages. Please let us know if you have any problems, suggestions, or comments.
We have updated the look of the Files page. Please let us know if you have any problems, suggestions, or comments.
Currently, we do not limit the disk space used by a project. Unless this is abused, we have no plans to change this policy.
We do not allow shell access to our servers. We do not plan to allow this in the future.
We have a cluster of servers we use for creating RPM files. It includes compiling from source, but is focused on packaging, not just compiling. For more information, you can read about it in the Docs section -- our BrainShare presentations are in the General section, and the web service provided by Novell Forge is described in the Web Service section.
You can download an Eclipse plug-in to use this service in the Files section, and we are working on integrating this feature into the website. For more information on our packaging service, you can visit the Ximian Build Buddy project hosted on Forge.
</p>
The forge site now has anonymous ftp access for all public file downloads. This means that you can now download file releases from ftp.novell.com. You will find file release is the following directory structure. pub/forge/<project short name>/
The forge website is teaming up with Ximian Build Buddy and Red Carpet to create a dream development environment. In the works is the ability, from eclipse, to submit your cvs repository to Build Buddy to build and package your application for some of the standard linux distros. After that, submitted them to forges own Red Carpet server to distribute you app to your user base. We have most of the api defined and part of it implimented. You will be able to see a live demo of this at BrainShare. Stop by the One Net solutions lab while you are there and we will help you set up your build environment as well. Look for more information on the api soon.
-The Forge Team
ViewCVS has had its problems in the last few months staying up. We have upgraded viewcvs and set it behind apache so it should be able to handle requests much better now. CVS graph and code coloring has also been added to make viewcvs a little nicer to use.
paul
In the admin file release section of a project:
package names are now changable. packages can be deleted. releases can be deleted.
In the admin file release section of a project:
package names are now changable. packages can be deleted. releases can be deleted.
The source code used for Novell Forge is now available for perusal and anonymous checkout. Follow the CVS link in the project menu for information.
© 2009 Novell, Inc. All Rights Reserved.
