Revision history for AnOpenNICProject
Revision [3755]
Last edited on 2016-05-30 22:49:37 by CalumMcAlinden [Replaces old-style internal links with new pipe-split links.]Additions:
~-[[http://git.opennic.glue/ | Code repositories]]
Deletions:
Revision [3245]
Edited on 2014-08-12 07:23:48 by CalumMcAlinden [Replaces old-style internal links with new pipe-split links.]Additions:
Any OpenNIC related project should have the following on their Wiki page;
~-[[http://git.opennic.glue/ Code repositories]]
An OpenNIC project is should be open source as OpenNIC will not endorse close source projects.
~-[[http://git.opennic.glue/ Code repositories]]
An OpenNIC project is should be open source as OpenNIC will not endorse close source projects.
Deletions:
~- Code repos
It is recommened that the OpenNIC support center be used to track the project. If you are the leader of an OpenNIC related project please send an email to tasks@opennicproject.org. In this email please include the following;
~- Project name in the subject header
~- A description of the project in the message body
You will then be emailed back a confirmation email stating that the ticket has been logged. The important part of the reply message you need to note down is the new subject line. [OpenNIC #XX] will be contained in the subject header, this needs to be included in any emails back to tasks@opennicproject.org in order to have any updates logged about the project.
I.E [OpenNIC #45] - Updated user password authentication
By using the OpenNIC Support center to report project updates to, others are then able to see the progress of the project. An OpenNIC project is required to be 100% open source. If you do not aggree with this, please do not partake in any OpenNIC project work as OpenNIC will not endorse close source projects.
Additions:
By using the OpenNIC Support center to report project updates to, others are then able to see the progress of the project. An OpenNIC project is required to be 100% open source. If you do not aggree with this, please do not partake in any OpenNIC project work as OpenNIC will not endorse close source projects.
Deletions:
Revision [1472]
Edited on 2008-06-08 14:36:19 by JulianDemarchi [Added not about opennic and open source]Additions:
By using the OpenNIC Support center to report project updates to, others are then able to see the progress of the project. An OpenjNIC project is required to be 100% open source. If you do not aggree with this, please do not partake in any OpenNIC project work as OpenNIC will not endorse close source projects.
Deletions:
Additions:
This page contains information in regards to what OpenNIC would like to see from a member whilst they are running an OpenNIC related project. If you have any suggestions for this page please feel free to add them.
Any OpenNIC related project should have the following on their WIKI page;
~- A roadmap for the project
~- A plan of the project
As progress continues the project should have at their disposal;
~- A test bed to demonstrate
OpenNIC is happy to try and help provide resources for a project, including;
~- Test beds
~- Code repos
If your project requires any resources that OpenNIC may be able to provide please send an email to support@opennicproject.org
It is recommened that the OpenNIC support center be used to track the project. If you are the leader of an OpenNIC related project please send an email to tasks@opennicproject.org. In this email please include the following;
~- Project name in the subject header
~- A description of the project in the message body
You will then be emailed back a confirmation email stating that the ticket has been logged. The important part of the reply message you need to note down is the new subject line. [OpenNIC #XX] will be contained in the subject header, this needs to be included in any emails back to tasks@opennicproject.org in order to have any updates logged about the project.
I.E [OpenNIC #45] - Updated user password authentication
By using the OpenNIC Support center to report project updates to, others are then able to see the progress of the project.
Any OpenNIC related project should have the following on their WIKI page;
~- A roadmap for the project
~- A plan of the project
As progress continues the project should have at their disposal;
~- A test bed to demonstrate
OpenNIC is happy to try and help provide resources for a project, including;
~- Test beds
~- Code repos
If your project requires any resources that OpenNIC may be able to provide please send an email to support@opennicproject.org
It is recommened that the OpenNIC support center be used to track the project. If you are the leader of an OpenNIC related project please send an email to tasks@opennicproject.org. In this email please include the following;
~- Project name in the subject header
~- A description of the project in the message body
You will then be emailed back a confirmation email stating that the ticket has been logged. The important part of the reply message you need to note down is the new subject line. [OpenNIC #XX] will be contained in the subject header, this needs to be included in any emails back to tasks@opennicproject.org in order to have any updates logged about the project.
I.E [OpenNIC #45] - Updated user password authentication
By using the OpenNIC Support center to report project updates to, others are then able to see the progress of the project.
