SourceForge.net

Logged In: YES
user_id=152443

Greetings,

The SourceForge.net team has reviewed this request for hosting.
OS distributions are among the largest projects, in terms of disk
space and bandwidth requirements for us to serve file releases.

The focus of SourceForge.net is in providing hosting for Open
Source software development projects. The amount of software
developed by software distribution projects is typically limited
compared to the amount of material they are simply redistributing.

Our site is designed for hosting software development projects;
our file release system is not currently well suited to projects
that need to release large numbers of separate packages and
update those releases frequently. Along with our goal of
providing hosting for Open Source software development
activities, we also place significant focus on retaining all file
releases a project makes; with distro releases typically
exceeding 500MB for a single release, maintaining the full
historical work of such a project does pose significant problems
with regard to disk consumption.

SourceForge.net is operated with a finite amount of resources;
since our mission is to support Open Source software development
projects, not projects that are primarily redistributing existing
software, we strictly limit the number of large distribution
projects we provide hosting to.

At this time, we are unable to honor your request for hosting.

Should you have further questions or concerns regarding this
matter, please add a comment to this request.

Thank you,

Jacob Moorman
Quality of Service Manager, SourceForge.net

Logged In: YES
user_id=1008913

Hi,

I am still waiting for your review

Regards
Sunil

Logged In: YES
user_id=1008913

Thanks for your kind response, and for considering the project.

> 1. How frequently do you expect to be updating packages within
your tree?

With every release of major packages like apache, kde, gnome, kernel,
gaim,
etc. And with every release of new distribution. Down the line, we also
wish to
provide interface to user to add a package and review it.

> 2. Do you plan to also provide full releases in an ISO file
format (or similar)?

No, we will only provide global configuration file which will be used by
our
program that will run on users machine. The program will provide interface
for
package selection using the configuration file. And based on the
selections
user made, the packages will be downloaded and a distribution ( basically
ISO)
will me made out of that.
We can only provide configuration files which are pre configured for a
particular setup. Most popular and useful setups like server, workstation,
mini,
etc can be given as configurtion files. So the user does not even need to
go
through package selection.

> 3. How many members of your team will be directly updating the
package tree?

Right now we are two members. We look forward for more people to join
after
we get the project registered at sf. We would like people using
distribution to
join us so that we could provide this service to all distribution types.

> 4. How many distinct versions or quality delineations do you
intend to maintain (i.e. stable, unstable, testing, etc.)?

We would like to keep say last 5 version of stable releases and last
testing
release.

> 5. What mechanism will your end-users be using to update their
local package load?

I didnot get the question. After the user has made his distribution, its
like any
other distribution.
But we also want to incooperate upgrade tool, with could use our
configuration
file.

> 6. How many packages do you expect to exist in each tree (as
described in #4)?

Equal to that provided by the distribution.

> 7. What do you estimate to be your maximal space requirement for
all materials you intend to provide?

Few MBs. Other than the project only the configuratin files need to be
saved.
We are not saving any packages, we will only provide the download
locations
to the packages in our configuration file.

> 8. Are all materials you are providing under an Open Source
license?

Need not be. Our configuration file may contain entries for non Open
Source
softwares like Opera, ymessenger, etc.

> 9. Does your project intend to make use of our project CVS
services?

Yes, we would like to use cvs to update our project and the configuration
files.

> 10. What other SourceForge.net features will your project be
using?

Thats it. Maybe a homepage.

Regards
Sunil

Logged In: YES
user_id=597273

Greetings,

Please provide answers to these questions:

1. How frequently do you expect to be updating packages within
your tree?

2. Do you plan to also provide full releases in an ISO file
format (or similar)?

3. How many members of your team will be directly updating the
package tree?

4. How many distinct versions or quality delineations do you
intend to maintain (i.e. stable, unstable, testing, etc.)?

5. What mechanism will your end-users be using to update their
local package load?

6. How many packages do you expect to exist in each tree (as
described in #4)?

7. What do you estimate to be your maximal space requirement for
all materials you intend to provide?

8. Are all materials you are providing under an Open Source license?

9. Does your project intend to make use of our project CVS services?

10. What other SourceForge.net features will your project be using?


This will help us to ensure the needs of your project are met by
the services provided by SourceForge.net to your project.

Thank you,

SouceForge.net Support

Logged In: YES
user_id=597273

Greetings,

As stated during the project registration process, you are to
submit a Support Request for a rejected project not reregister
the project again. There are multiple reasons for this, the one
that affects you the most is that it causes significant delays in
the processing of your rejection and trying to convert it to an
accepted project. For this reason and others we highly suggest
that you read our instructions carefully and follow them for the
fastest turnaround on your issues.

Thank you,

SourceForge.net Support