PhilipCain

Differences between revisions 20 and 22 (spanning 2 versions)
⇤ ← Revision 20 as of 2005-09-29 21:38:15 →
Size: 2911
Editor: 208-47-135-198
Comment: added bug 13525
← Revision 22 as of 2006-04-05 22:02:29 → ⇥
Size: 4621
Editor: ip250
Comment: created churchubuntu braindump
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * Blog: http://www.philipandjenny.com  * Blog: http://www.philipcain.com
Line 7: Line 7:

Hi, my name is Philip Cain. I'm 22 and you could call me an IT systems administrator and webmaster. Kubuntu is the primary OS on my desktop at home, and I hope to assimilate more desktops and servers at work. I plan on helping the Ubuntu community, and specifically the Kubuntu project, in any way I can. I'll do this mostly by adopting threads in the forums, adding [:HowTos: HowTo] wikis, cleaning the wiki, reporting/fixing bugs, creating artwork, answering questions on #kubuntu, and helping with documentation. Another area I'd like to help in is eliminating the "last mile" of required CLI usage from within Kubuntu.
Line 35: Line 33:
== Personal Kubuntu TODO (Updated for Dapper) == = ChurchUbuntu =
Until we find a home in the wiki or somewhere else on the web, this will be the braindump area for a possible Ubuntu derivative for poor churches in Mexico and South America (or possibly anywhere).
Line 37: Line 36:
 * Improve Adept
 * Integrate [https://bugs.kde.org/show_bug.cgi?id=106582 SnippetBooks] into Kate (or kdeaddons kate-plugins)
 * Gecko rendering engine for [http://www.kdedevelopers.org/node/view/976 Konqueror] (KDE4)		 == Rationale ==
There are hundreds of churches and organizations in Mexico (specifically) and around the world which cannot afford computers, software or any other technology. An Ubuntu derivative, created specifically to cater to these organizations, would make the donation process much smoother (no licensing issues, necessary software is prepared).
Line 41: Line 39:
''The Last Mile - Removing the Command Line Interface'' == Use cases ==
1. An old computer (Gateway PIII 1GHZ with 128MB RAM) was recently donated for the purpose of providing a poor church in Mexico with some technology. Software needs to be prepared for this computer to be usable. A CD based on Xubuntu, with a metapackage that provides the Sword library and a Spanish translation of the Bible, would be perfect for this situation.
Line 43: Line 42:
 * [http://kconfigure.sourceforge.net/ KConfigure]. Fixes need for configure, make, make install, and/or checkinstall commands. (suggested on KubuntuSuggestedPackages)
 * [http://kde-apps.org/content/show.php?content=23761 KSystemLog]. Fixes need for tailing /var/log files.		 (add more use cases)
Line 46: Line 44:
== Availability ==
Part-time only; my full-time IT job and my family keeps me busy.		 == Process Considerations ==

=== Distribution ===
We need to decide if this should be a full blown derivative ("ChurchUbuntu"), in which case we would follow the [:DerivativeDistroProcess: Derivative Distro Process], or if it would simply be a metapackage which could be made available on CD and on the web. Using a metapackage (churchubuntu-desktop) would be the easiest method. A base (server) installation of Ubuntu can be prepared on a computer, then the churchubuntu-desktop package can be installed from another CD (which includes all the appropriate packages).

=== Metapackage ===
If we decide to use the metapackage method (churchubuntu-desktop), packages need to be decided upon. The following packages in Main and Universe have been proposed (add to this list as necessary):

 || xubuntu-desktop, libsword5c2a, gnomesword, sword-comm-mhcc, sword-comm-pers, sword-comm-scofield, sword-comm-tdavid, sword-dict-naves, sword-dict-strongs-greek, sword-dict-strongs-hebrew, sword-text-kjv, sword-text-sparv, sword-text-web ||

The next step would be to prepare custom work specifically to fit the needs of our use cases. This might include custom artwork/branding, file templates, sample files, Creative Commons music, etc.

=== Collaboration ===
We should use the Ubuntu-provided collaboration facilities to make this process as smooth as possible. This includes possibly creating a separate wiki page (ChurchUbuntu), a discussion thread for ideas in the [http://www.ubuntuforums.org forum], and maybe even a informative spec on [http://www.launchpad.net Launchpad].

There is also some basic interest in this area: http://www.thelinuxlink.net/l4c/news.html

We should explore the possibility of a partnership (if appropriate) with the "Linux 4 Christians" group.

=== Branding ===
Before collaboration can really begin, a draft branding/naming scheme must be decided. For the use of this braindump, ChurchUbuntu was appropriate, but there may be a better name, especially if this project isn't intended for churches in general.

About Me

Contributions and Projects

Wiki Cleanup

Wiki Articles

  • [:SagerNP3760Hoary:Kubuntu Hoary 5.04 on a Sager NP3760 Laptop] (started)

Bugs I've Reported/Commented/Closed

ChurchUbuntu

Until we find a home in the wiki or somewhere else on the web, this will be the braindump area for a possible Ubuntu derivative for poor churches in Mexico and South America (or possibly anywhere).

Rationale

There are hundreds of churches and organizations in Mexico (specifically) and around the world which cannot afford computers, software or any other technology. An Ubuntu derivative, created specifically to cater to these organizations, would make the donation process much smoother (no licensing issues, necessary software is prepared).

Use cases

1. An old computer (Gateway PIII 1GHZ with 128MB RAM) was recently donated for the purpose of providing a poor church in Mexico with some technology. Software needs to be prepared for this computer to be usable. A CD based on Xubuntu, with a metapackage that provides the Sword library and a Spanish translation of the Bible, would be perfect for this situation.

(add more use cases)

Process Considerations

Distribution

We need to decide if this should be a full blown derivative ("ChurchUbuntu"), in which case we would follow the [:DerivativeDistroProcess: Derivative Distro Process], or if it would simply be a metapackage which could be made available on CD and on the web. Using a metapackage (churchubuntu-desktop) would be the easiest method. A base (server) installation of Ubuntu can be prepared on a computer, then the churchubuntu-desktop package can be installed from another CD (which includes all the appropriate packages).

Metapackage

If we decide to use the metapackage method (churchubuntu-desktop), packages need to be decided upon. The following packages in Main and Universe have been proposed (add to this list as necessary):

  • xubuntu-desktop, libsword5c2a, gnomesword, sword-comm-mhcc, sword-comm-pers, sword-comm-scofield, sword-comm-tdavid, sword-dict-naves, sword-dict-strongs-greek, sword-dict-strongs-hebrew, sword-text-kjv, sword-text-sparv, sword-text-web

The next step would be to prepare custom work specifically to fit the needs of our use cases. This might include custom artwork/branding, file templates, sample files, Creative Commons music, etc.

Collaboration

We should use the Ubuntu-provided collaboration facilities to make this process as smooth as possible. This includes possibly creating a separate wiki page (ChurchUbuntu), a discussion thread for ideas in the [http://www.ubuntuforums.org forum], and maybe even a informative spec on [http://www.launchpad.net Launchpad].

There is also some basic interest in this area: http://www.thelinuxlink.net/l4c/news.html

We should explore the possibility of a partnership (if appropriate) with the "Linux 4 Christians" group.

Branding

Before collaboration can really begin, a draft branding/naming scheme must be decided. For the use of this braindump, ChurchUbuntu was appropriate, but there may be a better name, especially if this project isn't intended for churches in general.

CategoryHomepage

PhilipCain (last edited 2008-08-06 16:29:43 by localhost)