I would like to propose adding project directories under http://www.openfabrics.org/downloads/ where appropriate and give maintainers access. For example:

Jeff, please add the following directories with maintainer access as follow (or grant access at a maintainer group level):

http://www.openfabrics.org/downloads/verbs (rdreier)
http://www.openfabrics.org/downloads/rdmacm (shefty)
http://www.openfabrics.org/downloads/dapl (ardavis)
http://www.openfabrics.org/downloads/sdp (eitan)
http://www.openfabrics.org/downloads/utils (eitan)
http://www.openfabrics.org/downloads/management (sashak)
http://www.openfabrics.org/downloads/OFED (vlad)
http://www.openfabrics.org/downloads/archives (vlad)
http://www.openfabrics.org/downloads/WinOF (ssmith) (Stan Smith will need an account)
http://www.openfabrics.org/downloads/hw/mthca (rdreir)
http://www.openfabrics.org/downloads/hw/mlx4 (rdreir)
http://www.openfabrics.org/downloads/hw/ehca (raisch)
http://www.openfabrics.org/downloads/hw/ipath (ralphc)
http://www.openfabrics.org/downloads/hw/cxgb3 (ralphc)
http://www.openfabrics.org/downloads/mpi/mvapich (pasha)
http://www.openfabrics.org/downloads/mpi/mvapich2 (rowland)
http://www.openfabrics.org/downloads/mpi/openmpi (jsquyres)

Let us know when these directories are created and the maintainers, who want to expose their packages via the webpage, will create a README that details the contents of the directory along with WEB_README that provides a short description for the webpage.

Will this format allow you to auto configure the download webpage sufficiently? The idea is to only add links/descriptions to those project sub-directories with WEB_README files present.

Please advise if something on the list is wrong or we missed a project.

Thanks,

-arlin


_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Reply via email to