Difference between revisions of "Projects"

From ProgClub
Jump to: navigation, search
(Motorcycle Parts - OEM Or Aftermarket?)
 
(48 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This is definitely always a difficult one particular to answer when shopping for motorcycle parts and I firmly believe that every one of us must decide what'ersus best for our bikes AFTER carefully evaluating each and every of the choices.  
+
This page provides information about ProgClub's free software computer programming and systems administration projects. See [[TODO]] for ideas about what to work on. For information about ProgClub domains, see [[Domains]]. For information about member services, see [[Services]]. For information about hosts on the ProgClub network, see [[Machines]]. Check out our [[Forums]] to get in touch.
+
 
For me?  
+
= Looking for something to do? =
+
 
Well... it really depends on what We are looking for - just substitution or improvement - , the opportunity of the element, my budget along with other things. Sometimes I buy OEM, others aftermarket motorcycle parts.  
+
If you're looking for something to do you can browse our projects below, or there's a section on the website: [[TODO]]. The TODO section is there to give you a few ideas about things that it would be nice to get done. It's not comprehensive. If you have ideas feel free to make a note of them.
+
 
Keep reading. You will find some views that will with any luck , help you decide the next time you purchase for motorcycle parts.  
+
= Starting a ProgClub project =
+
 
What a heck are OEM parts?
+
If you want to start a project, then: give the project a name, reference the project from this page (put it in the [[#Active_projects|active projects]] or [[#Prospective_projects|prospective projects]] section as appropriate) and copy the [https://www.progclub.org/pcwiki/index.php?title=Project_template&action=edit project template] to get you started. You might also like to know about how to [[Subversion#Creating_new_projects|create your project in pcrepo]].
+
 
OEM parts means Unique Gear Manufacturer parts which not necessarily mean the OM (Authentic Manufacturer) actually produced them. You realize, many motorcycle and automobile manufacturers don'testosterone manufacture each and every in the parts used in the vehicles. These people frequently have the parts designed and manufactured by outside independent companies and, install them of their machines or place them of their personal boxes to end up being sold as OEM parts!
+
You should know that we have a spec concerning [[versioning]] of our projects.
+
 
Good to know when buying OEM Motorcycle Parts:  
+
= Software configuration management =
+
 
When you buy OEM Motorcycle Parts you are buying the exact same initial portion the manufacturer used set up your motorcycle, which means:  
+
You can read about ProgClub's [[SCM|Software Configuration Management]].
+
 
>> Same efficiency because the part installed in your motorcycle right right now. The portion won'testosterone always be better nor worse than the unique component you need to replace.  
+
= Projects =
+
 
>> Normally OEM parts a more (sometimes Far more) expensive than aftermarket parts.  
+
== Active projects ==
+
 
>> Motorcycle and car agencies clerks will normally notify you OEM Parts are higher leading and the finest option for replacements. Is actually this true? Well at times it is actually, sometimes it'utes not.  
+
Current ProgClub projects are:
+
 
>> Normally following a selected period of energy, the manufacturer lets the business that initially designed/produced the portion to sell it in their personal box at a significantly lower cost, making it: a very Aftermarket OEM component! :-)  
+
* [[Text tables (TTB)]], the ProgClub structured data format.
+
* [[PcLog]], the ProgClub event logger.
>> End up being Watchful if your bike will be still in its guarantee period make sure you use only OEM parts and have them installed by authorized mechanics. If you don'capital t carry out so, you will probably void the guarantee.  
+
* [[PHPBOM]], the PHP Ball Of Mud (a PHP web-framework and toolkit).
+
* [[x2maths.web]], a maths website.
What about Aftermarket parts?
+
* [[Migration 2016]], a sysadmin project to upgrade the ProgClub infrastructure.
+
* [[ProgClub.js]], for ProgClub standard JavaScript formatting.
Aftermarket parts should perform along with OEM parts but are produced by companies other than the original manufacturer(ersus).  
+
* [[Pcformcheck]], for validating/testing your HTML forms.
+
* [[Pchtmlcheck]], for validating your HTML.
Things to realize when buying Aftermarket Motorcycle Parts:
+
* [[Pccipher firefox addon]], for Firefox crypto fun.
+
* [[Pcwebstats]], to collect HTTP stats.
>> MAKE SURE YOUR GUARANTEE PERIOD Will be OVER. In many cases, you can VOID your guarantee if you have a good aftermarket part installed by a great unauthorized mechanic in your own device. I understand I said it before, but it's worth repeating; I came about to us! :-(
+
* [[Pcsvnrelease]], to provide version and release management for projects.
+
* [[Pcweblink]], to private a HTTP redirection and linking service.
>> Equivalent aftermarket Suzuki motorcycle parts are normally low-priced than OEM parts. At times as much as 70% less costly!
+
* [[Slib]], to provide the PHP framework for Sgen. Sgen is a Blackbrick product.
+
* [[Pcad]], to provide a daemon that can be asked to do things on behalf of non-privileged users.
>> Aftermarket parts can have lower,the same or higher good quality than the original.  
+
* [[JsPHP]], to provide PHP functions in Javascript.
+
* [[Pcphpjs]], to provide the CMS for [[JsPHP]].
>> When buying aftermarket parts make sure you are taking AT LEAST the same high quality since the OEM part. If at all try to get some reviews about brands and overall performance. That you can do it in the Internet, with your favourite mechanic or with fellow riders.  
+
* [[Pcmnet]], to provide MemberNet and MobileNet.
+
* [[Pcwiki]], to provide the ProgClub wiki.
>> If you are looking for high efficiency parts and devices, you understand the kind: carbon fiber, titanium, aerospace aluminum parts and gizmos, well you will likely find them when aftermarket motorcycle parts.
+
* [[Network administration]], to provide network services.
+
 
OEM or aftermarket motorcycle parts, sooner or later you may be shopping for them...  
+
== Other projects ==
+
 
Benefit from the ride!
+
Projects that ProgClub are helping with that are not ProgClub projects:
+
 
Daniel Levy, contributing writer of http://www.japanesemotorcyclesworld.com
+
* [[GNUrc]], for [https://www.gnurc.com/ GNU Remote Control]
http://www.highfivetour.com/index.php/member/11220/
+
 
 +
== Prospective projects ==
 +
 
 +
Projects that are only in their planning phase are recorded here. Maybe one day they'll make it to real live active projects, but until then we won't kid ourselves.
 +
 
 +
* [[MyInternetShortcuts]], manage your shortcuts across all your devices.
 +
* [[WebDefinitions]], a personal assistant.
 +
* [[Gitweb hackathon]], to migrate ProgClub svn to git.
 +
* Pddr, to provide a dance school membership management system.
 +
* Pcsymbol, to document and explain mathematical symbols and Unicode character codes.
 +
* Pcloan, to record details of who has borrowed what. Maybe integrate with Pcbook?
 +
* Pcbook, to manage and document our collective library of books.
 +
* [[Cweb]], to make a distributed search-engine.
 +
* [[HackTrap]], to create a website designed to trap and find hackers. But not users. Really, just hack hackers. (OK, I'll see what we can do. [[User:John|JE]])
 +
 
 +
== Completed projects ==
 +
 
 +
Stuff that's finished. Latest on top.
 +
 
 +
* [[JJcode]], for key management in your applications.
 +
* [[QuitFirefoxAtTime]], for closing your Firefox tab after a timeout.
 +
* [[cdr]], change directory with regular expressions.
 +
* [[rdfind.php]], redundant data processor in PHP.
 +
* [[SAK2014]], Standard Access Keys for web browsers.
 +
* [[img2data]], for converting image files to Data URIs.
 +
* [[Pcforever]], a caching HTTP gateway.
 +
* [[Pcrego]], to provide web-based ProgClub registration.
 +
* [[Jsrun]], for Shawn's JScript.NET utilities.
 +
* [[Pcdate]], the ProgClub date scheduler.
 +
* [[Pcpics]], for the ProgClub photo gallery.
 +
* [[JJ5-test|jj5-test]], for [[User:John|John]]'s experiments.
 +
* [[Pcwebmail]], to provide webmail facilities at ProgClub.
 +
* [[Pcweb]], to provide the ProgClub web-site.
 +
* [[Email]], to get email and the [[mailing lists]] functional.
 +
* [[Pcmail]], to provide email administration.
 +
* [[Pccipher]], to provide compatible encryption libraries for many platforms.
 +
* [[Single sign-on]], to get user logins working.
 +
* [[JJ5-bin|jj5-bin]], to provide administration and utility scripts.
 +
* [[Pcview]], to provide a web-based svn viewer.
 +
* [[Pcldap]], to provide LDAP administration.
 +
* [[Pcblog]], to provide blogs.
 +
* [[Pcma]], to provide database administration.
 +
* [[Kerberos]], to provide authentication services.
 +
 
 +
== Cancelled projects ==
 +
 
 +
Stuff that we're not doing. Latest on top.
 +
 
 +
* [[Psweb]], for personalserver.com.
 +
* [[IPSec]], to secure the network. Cancelled.
 +
 
 +
= Contributing to ProgClub projects =
 +
 
 +
Contributions to ProgClub projects are covered by the [[ProgClub:Copyrights|Copyright policy]]. Generally in order to contribute to a ProgClub project you need to be a member. That is unless you are only planning to contribute to a [[Forums|forum]] such as the project page on the wiki. Contributions to ProgClub forums are also covered by the [[ProgClub:Copyrights|Copyright policy]]. If you are a member and you contribute to a ProgClub project a link to your user page will be added to the Contributors section of the project page. If you contribute to a ProgClub project and your are not a member, then you can optionally include your details (a link to your user page if you have an account on the wiki (you don't need to be a member to have one of these), your email address, or a link to your web-site) along with your name in the Contributors section.
 +
 
 +
== Releasing ProgClub projects ==
 +
 
 +
About half of ProgClub's projects have source-code in the [http://www.progclub.org/pcrepo/ subversion repository]. Projects that don't have code in the repository don't really need to be released, for them you just have to update the project documentation on the wiki. Projects in svn do need to be released, however. There is a process for releasing projects in svn, and it's detailed on the [[Subversion]] page.
 +
 
 +
In addition to doing a subversion release (which tags the release and updates the latest tag) you might also like to deploy the software. To do a deployment use the project-specific release script in /home/jj5/bin. At the moment that is any of:
 +
 
 +
* release-pcwiki, for releasing [[pcwiki]]
 +
* release-pcblog, for releasing [[pcblog]]
 +
* release-pcldap, for releasing [[pcldap]]
 +
* release-pcma, for releasing [[pcma]]
 +
* release-pcview, for releasing [[pcview]]
 +
* release-pccipher, for releasing [[pccipher]]
 +
* release-pcweb, for releasing [[pcweb]]
 +
* release-pcmnet, for releasing [[pcmnet]]
 +
 
 +
This list will be added to as time goes by, and as there is a need for doing new project releases.
 +
 
 +
When calling a project-specific release script you pass a single parameter; that being the 'comment', or 'release notes', for the release you are doing. You run these scripts on [[charity]], and after doing the subversion release the web software in /var/www/ is updated appropriately.

Latest revision as of 15:06, 11 December 2017

This page provides information about ProgClub's free software computer programming and systems administration projects. See TODO for ideas about what to work on. For information about ProgClub domains, see Domains. For information about member services, see Services. For information about hosts on the ProgClub network, see Machines. Check out our Forums to get in touch.

Looking for something to do?

If you're looking for something to do you can browse our projects below, or there's a section on the website: TODO. The TODO section is there to give you a few ideas about things that it would be nice to get done. It's not comprehensive. If you have ideas feel free to make a note of them.

Starting a ProgClub project

If you want to start a project, then: give the project a name, reference the project from this page (put it in the active projects or prospective projects section as appropriate) and copy the project template to get you started. You might also like to know about how to create your project in pcrepo.

You should know that we have a spec concerning versioning of our projects.

Software configuration management

You can read about ProgClub's Software Configuration Management.

Projects

Active projects

Current ProgClub projects are:

  • Text tables (TTB), the ProgClub structured data format.
  • PcLog, the ProgClub event logger.
  • PHPBOM, the PHP Ball Of Mud (a PHP web-framework and toolkit).
  • x2maths.web, a maths website.
  • Migration 2016, a sysadmin project to upgrade the ProgClub infrastructure.
  • ProgClub.js, for ProgClub standard JavaScript formatting.
  • Pcformcheck, for validating/testing your HTML forms.
  • Pchtmlcheck, for validating your HTML.
  • Pccipher firefox addon, for Firefox crypto fun.
  • Pcwebstats, to collect HTTP stats.
  • Pcsvnrelease, to provide version and release management for projects.
  • Pcweblink, to private a HTTP redirection and linking service.
  • Slib, to provide the PHP framework for Sgen. Sgen is a Blackbrick product.
  • Pcad, to provide a daemon that can be asked to do things on behalf of non-privileged users.
  • JsPHP, to provide PHP functions in Javascript.
  • Pcphpjs, to provide the CMS for JsPHP.
  • Pcmnet, to provide MemberNet and MobileNet.
  • Pcwiki, to provide the ProgClub wiki.
  • Network administration, to provide network services.

Other projects

Projects that ProgClub are helping with that are not ProgClub projects:

Prospective projects

Projects that are only in their planning phase are recorded here. Maybe one day they'll make it to real live active projects, but until then we won't kid ourselves.

  • MyInternetShortcuts, manage your shortcuts across all your devices.
  • WebDefinitions, a personal assistant.
  • Gitweb hackathon, to migrate ProgClub svn to git.
  • Pddr, to provide a dance school membership management system.
  • Pcsymbol, to document and explain mathematical symbols and Unicode character codes.
  • Pcloan, to record details of who has borrowed what. Maybe integrate with Pcbook?
  • Pcbook, to manage and document our collective library of books.
  • Cweb, to make a distributed search-engine.
  • HackTrap, to create a website designed to trap and find hackers. But not users. Really, just hack hackers. (OK, I'll see what we can do. JE)

Completed projects

Stuff that's finished. Latest on top.

  • JJcode, for key management in your applications.
  • QuitFirefoxAtTime, for closing your Firefox tab after a timeout.
  • cdr, change directory with regular expressions.
  • rdfind.php, redundant data processor in PHP.
  • SAK2014, Standard Access Keys for web browsers.
  • img2data, for converting image files to Data URIs.
  • Pcforever, a caching HTTP gateway.
  • Pcrego, to provide web-based ProgClub registration.
  • Jsrun, for Shawn's JScript.NET utilities.
  • Pcdate, the ProgClub date scheduler.
  • Pcpics, for the ProgClub photo gallery.
  • jj5-test, for John's experiments.
  • Pcwebmail, to provide webmail facilities at ProgClub.
  • Pcweb, to provide the ProgClub web-site.
  • Email, to get email and the mailing lists functional.
  • Pcmail, to provide email administration.
  • Pccipher, to provide compatible encryption libraries for many platforms.
  • Single sign-on, to get user logins working.
  • jj5-bin, to provide administration and utility scripts.
  • Pcview, to provide a web-based svn viewer.
  • Pcldap, to provide LDAP administration.
  • Pcblog, to provide blogs.
  • Pcma, to provide database administration.
  • Kerberos, to provide authentication services.

Cancelled projects

Stuff that we're not doing. Latest on top.

  • Psweb, for personalserver.com.
  • IPSec, to secure the network. Cancelled.

Contributing to ProgClub projects

Contributions to ProgClub projects are covered by the Copyright policy. Generally in order to contribute to a ProgClub project you need to be a member. That is unless you are only planning to contribute to a forum such as the project page on the wiki. Contributions to ProgClub forums are also covered by the Copyright policy. If you are a member and you contribute to a ProgClub project a link to your user page will be added to the Contributors section of the project page. If you contribute to a ProgClub project and your are not a member, then you can optionally include your details (a link to your user page if you have an account on the wiki (you don't need to be a member to have one of these), your email address, or a link to your web-site) along with your name in the Contributors section.

Releasing ProgClub projects

About half of ProgClub's projects have source-code in the subversion repository. Projects that don't have code in the repository don't really need to be released, for them you just have to update the project documentation on the wiki. Projects in svn do need to be released, however. There is a process for releasing projects in svn, and it's detailed on the Subversion page.

In addition to doing a subversion release (which tags the release and updates the latest tag) you might also like to deploy the software. To do a deployment use the project-specific release script in /home/jj5/bin. At the moment that is any of:

  • release-pcwiki, for releasing pcwiki
  • release-pcblog, for releasing pcblog
  • release-pcldap, for releasing pcldap
  • release-pcma, for releasing pcma
  • release-pcview, for releasing pcview
  • release-pccipher, for releasing pccipher
  • release-pcweb, for releasing pcweb
  • release-pcmnet, for releasing pcmnet

This list will be added to as time goes by, and as there is a need for doing new project releases.

When calling a project-specific release script you pass a single parameter; that being the 'comment', or 'release notes', for the release you are doing. You run these scripts on charity, and after doing the subversion release the web software in /var/www/ is updated appropriately.