PhilipCain

Differences between revisions 22 and 25 (spanning 3 versions)
Revision 22 as of 2006-04-05 22:02:29
Size: 4621
Editor: ip250
Comment: created churchubuntu braindump
Revision 25 as of 2006-05-29 01:10:21
Size: 4686
Editor: ip68-228-54-18
Comment: cleaned up buglist
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 * [http://www.kde-apps.org/content/show.php?content=23981 Kubuntu Package Menu] - This code is now included in Breezy within the kubuntu-default-settings
 * New
package testing (eventually here I'll be testing KDE 3.5 packages in Hoary and Breezy)
 * [http://www.kde-apps.org/content/show.php?content=23981 Kubuntu Package Menu] - This code was implemented in Breezy within the kubuntu-default-settings package
Line 15: Line 14:
    * http://lists.ubuntu.com/archives/ubuntu-doc/2005-June/002563.html (not yet implemented)
    * http://lists.ubuntu.com/archives/ubuntu-doc/2005-June/002601.html (not yet implemented)
    * http://lists.ubuntu.com/archives/ubuntu-doc/2005-June/002602.html (not yet implemented)
    * http://lists.ubuntu.com/archives/ubuntu-doc/2005-June/002563.html
    * http://lists.ubuntu.com/archives/ubuntu-doc/2005-June/002601.html
    * http://lists.ubuntu.com/archives/ubuntu-doc/2005-June/002602.html
Line 20: Line 19:
 * [:SagerNP3760Hoary:Kubuntu Hoary 5.04 on a Sager NP3760 Laptop] (started)  * [:LaptopTestingTeam/SagerNP3760: LaptopTestingTeam submission for Sager NP3760 Laptop]
Line 22: Line 21:
=== Bugs I've Reported/Commented/Closed === === Bugs I've Reported/Commented/Fixed ===
Line 24: Line 23:
 * https://bugzilla.ubuntu.com/show_bug.cgi?id=11436
 * https://launchpad.ubuntu.com/malone/bugs/440
 * https://bugzilla.ubuntu.com/show_bug.cgi?id=2497
 * https://bugzilla.ubuntu.com/show_bug.cgi?id=8681
 * https://launchpad.ubuntu.com/malone/bugs/815
 * https://bugzilla.ubuntu.com/show_bug.cgi?id=12034
 * https://bugzilla.ubuntu.com/show_bug.cgi?id=16651
 * https://bugzilla.ubuntu.com/show_bug.cgi?id=13525
 * https://www.launchpad.net/distros/ubuntu/+bug/440
 * https://www.launchpad.net/distros/ubuntu/+bug/815
 * https://www.launchpad.net/distros/ubuntu/+bug/9213
 * https://www.launchpad.net/distros/ubuntu/+bug/15001
 * https://www.launchpad.net/distros/ubuntu/+bug/17721
 * https://www.launchpad.net/distros/ubuntu/+bug/19767
 * https://www.launchpad.net/distros/ubuntu/+bug/22846
 * https://www.launchpad.net/distros/ubuntu/+bug/42518
 * https://www.launchpad.net/products/shipit/+bug/39265
Line 33: Line 33:
= ChurchUbuntu = = Chubuntu =
Line 40: Line 40:
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. 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, and Spanish language locale optimizations, would be perfect for this situation.
Line 47: Line 47:
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). We need to decide if this should be a full blown derivative ("Chubuntu"), 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 (chubuntu-desktop) would be the easiest method. A base (server) installation of Ubuntu can be prepared on a computer, then the xubuntu-desktop and chubuntu-desktop packages can be installed from another CD (which includes all the appropriate packages). It is highly possible that many of these computers will not have NICs, so comprehensive CD creation is high priority.
Line 50: Line 50:
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): If we decide to use the metapackage method (chubuntu-desktop), packages need to be decided upon. The following packages in Main and Universe have been proposed (add to this list as necessary):
Line 52: Line 52:
 || 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 ||  || 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 ||
Line 57: Line 57:
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]. We should use the Ubuntu-provided collaboration facilities to make this process as smooth as possible. This includes possibly creating a separate wiki page, a discussion thread for ideas in the [http://www.ubuntuforums.org forum], and maybe even a informative spec on [http://www.launchpad.net Launchpad].
Line 64: Line 64:
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. Before collaboration can really begin, a draft branding/naming scheme must be decided. For the use of this braindump, Chubuntu 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

  • [:LaptopTestingTeam/SagerNP3760: LaptopTestingTeam submission for Sager NP3760 Laptop]

Bugs I've Reported/Commented/Fixed

Chubuntu

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, and Spanish language locale optimizations, 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 ("Chubuntu"), 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 (chubuntu-desktop) would be the easiest method. A base (server) installation of Ubuntu can be prepared on a computer, then the xubuntu-desktop and chubuntu-desktop packages can be installed from another CD (which includes all the appropriate packages). It is highly possible that many of these computers will not have NICs, so comprehensive CD creation is high priority.

Metapackage

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

  • 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, 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, Chubuntu 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)