Stevens Todo Temp

Steven's Big List

On this page I will manage my list of things I want to accomplish over the next few months. This will include a TO DO list, Information & Link aggregation for later use, Random Notes to my self, & any other information I feel is useful to help evolve the wiki.

GOALS

1. Organize a single location with links to each of the 50 projects and their different variations
   1. EXAMPLE:
      1. Brick Press (this text links to the primary templated page we are creating/evolving)
         1. Version 1.1 (this text links to its main page)
         2. Version 0.8 (this text links to its main page)
      2. Each variation will have a way to link to purchase of kit with newest kit linked on primary page
2. Create (evolve) a universal Template for the primary page for each product
   1. Section Needs & Order
      1. Header Menu Bar
      2. Current Version
         1. Real Photo
         2. Icon
         3. Version History
      3. Skill sets to have (NOTE: Create list of skill sets then info on how to acquire them)
      4. Requirements to build
         1. Required/Recommended Tools
         2. Required OSE projects (from)
            1. Also, Uses which machines for operation
         3. Required of 500 core items
      5. Raw resources Required
   2. What requires this to build
   3. What does this create
      1. Example: CEB Bricks
   4. What bigger picture projects does this Enable
   5. Overview of project
   6. History of Project
   7. Specifications of Current Model
   8. CAD Files
   9. CAM Files
   10. Bill of Materials
   11. Build Instructions / Build Manual
   12. Link to Purchase
       1. Full Machine
       2. Build yourself kit
3. Build a page for the 500 parts
   1. break 500 out into 10-25 groups
   2. create a list of these groups
      1. links to page with all the items in that group
      2. Each item in the group links to a page to all the different variations
      3. Each variation links to a way to purchase
4. Create a SIMPLE single page for new people to the project
   1. Join Mailing List
   2. Open Source & OSE Ethos
   3. Watch Video - intro to GVCS 50
      1. Add On Boarding Playlist HERE
   4. How Can I help?
      1. I have Skills
         1. Fabrication
         2. CAD / 3D Design
         3. Programming
         4. Data Organization / Documentation
         5. Electronics
         6. Hydraulics
         7. Team Building
         8. Social Media / Marketing
      2. I have time to learn on my own
         1. Open Source Movement
         2. Documentation
         3. Building Skills
            1. Tools
            2. Framing
            3. Electrical
            4. Electronics
            5. Plumbing
            6. Hydraulics
            7. Programing
            8. CAD
            9. Textiles/Sewing
            10. Entrepreneurship
            11. Land Stewardship
            12. Humanity Stewardship
      3. I have resources to contribute
         1. Become a True Fan
         2. Buy a kit or working machine
      4. I have resources and time
         1. Join the Future Builders Academy
5. develop a funnel for new people (from first interest to full participation)
   1. Social Media
   2. Mailing list
   3. Join a community meeting
   4. Buy a product or join a class
   5. Contribute back
      1. Edit the wiki
      2. Update CAD files
      3. Start a local group
      4. Teach a skill/class
      5. Fill a core role with OSE
      6. Join the board of directors
6. Create a list of locations that need regular updating and develop a regular info update plan
   1. Website
      1. Home Page
   2. Wiki
      1. Home Page
   3. Projects
      1. GVCS 50
      2. Seed Eco Home(s)
   4. Find ALL places there are old dates for "current" info and update/remove
7. Research Board of Directors (potentially relaunch)
   1. Create a set of clear goals
   2. Build a Road map
      1. Financial plan/needs
      2. Prototype to commercial version 1.0 plan
         1. Order of importance
      3. Ideal roles to be filled for growth
8. Create a set of "playlists" for youtube videos
   1. GVCS Build Videos
   2. GVCS Adjacent Projects
   3. On-Boarding
   4. Entrepreneurship
   5. Home Building
   6. Classes
   7. Documentation
   8. Marketing & Branding
9. Create a list of educational videos from above and edit them down into quick information bites.
   1. Full videos into shorter versions of whole video with cleaned up audio and added graphics
   2. Quick videos 1 min or less, edited for verticals, for use on social media.
10. Set up a community meeting
    1. This would involve Marcin and the volunteers of the community
    2. use this as time to get feed back and inspire volunteers to do work that will bring us closer to our goals
11. Create a list of current communication channels and who is Administrator(s)
    1. Discord
    2. Forum
    3. Newsletter
    4. YouTube
    5. Facebook
    6. Research for any others
12. Create a list of collaborators past and present
    1. What projects they worked on
    2. Observable strengths
    3. Rank by participation
    4. Sort by Projects worked on
    5. gather any contact info as available
       1. Make a contact plan (once site/wiki are fresh)
          1. what they would like to see out of OSE
          2. What is/was their favorite thing about OSE
          3. What is/was their least favorite thing
          4. Would they be interested in collaborating more
             1. On what and/or what would have to be in place or different
13. Lay out the revenue channels for OSE
    1. Create a list of all the ways OSE can make revenue
    2. Build a visual representation of this
    3. Write 1-2 paragraphs describing how each revenue stream works
    4. Research revenue potential for each
14. Develop ideal operating budget for continues yearly operation
    1. Salaries
       1. CEO, COO, CFO, CMO, CTO
       2. Community Manager
       3. Educators
       4. Forman
       5. Engineer (open source stamping plans)
       6. Future Builders
    2. Bounties (rewards for tasks and initiative)
       1. Software bounties for code that solves problems
       2. Hardware Bounty for solving engineering build issues
       3. Documentation Bounties for documenting and updating information
    3. R&D
    4. Administrative costs
15. Build out Organization Chart
    1. Use Salaries as foundational map
    2. Show communication lanes
    3. include Annex Location in a 12 Locations Across the country
       1. Travel time to any Annex is 4 hours or less (no distance excuse)
16. Develop Curriculum outline
    1. A set of core classes and teaching resources to take a novice to a Future Builder
    2. Build in work study for those who can't afford to pay
       1. Onsite Building (easy to teach tasks)
       2. Shop Maintenance and Cleaning
       3. Grounds Maintenance
       4. Kit Assembly
       5. Order Fulfillment
       6. R&D Assistant
       7. Documentation
       8. Marketing
          1. Booth manning
          2. Social Media Content Creation

TO-DO

Working on GOALS 1 & 2 I have started the development of a dynamic index page along with a new template for projects. In this I have discovered the Wiki needs some additional tools so that data can be put in one location and used across the wiki. Therefor allowing a single point of data to be updated and it update across the whole site.

1. Install the following plugins for MediaWiki - Semantic MediaWiki - Semantic Result Formats - Page Forms

Below is the email I sent to Marcin requesting these installs and why they are needed.

Hello Marcin,

I’m working on improving and standardizing the Global Village Construction Set (GVCS) project pages on the Open Source Ecology wiki. To do this in a way that is easy to maintain long-term and accessible for future contributors, we need to install a small set of well-established MediaWiki extensions.These extensions are commonly used across MediaWiki installations and are designed to allow structured project data that can automatically populate index and navigation pages.Below is a short explanation of what is being requested and why, followed by step-by-step installation instructions.

EXTENSIONS REQUESTED

Semantic MediaWiki (Required)

What it does: Semantic MediaWiki allows wiki pages to store structured data such as project status, category, descriptions, images, and other metadata in a standardized format that can be automatically reused across pages.Why we need it: I am building a dynamic GVCS index page that will automatically list projects, display images, show status and descriptions, and update itself when new projects are added. Without Semantic MediaWiki, this would require constant manual editing and would not be sustainable. Current Status: Semantic MediaWiki does not appear to be installed based on the Special:Version page.

Semantic Result Formats

What it does: This extension adds additional display options for data stored using Semantic MediaWiki, including formatted lists, tables, and grid-style outputs.Why we need it: This will make it much easier to build clean project listing pages without requiring custom scripting or JavaScript.

Page Forms

What it does: Page Forms provides form-based editing for pages that use Semantic MediaWiki data. This allows contributors to fill out project details using dropdowns and simple form fields instead of editing raw wiki templates.Why we want it: This helps reduce editing mistakes and lowers the learning curve for contributors. It is not required immediately but would be beneficial long-term.

INSTALLATION INSTRUCTIONS

These instructions assume MediaWiki 1.39 or newer and that Composer is available on the server. Which the wiki already uses Composer-managed dependencies, so installing extensions requiring Composer should be consistent with the existing environment.STEP 1 – Install Semantic MediaWikiNavigate to the root directory of the MediaWiki installation.Run the Composer command to install Semantic MediaWiki version 4.    composer require mediawiki/semantic-media-wiki "~4.0" Next, open the file named LocalSettings.php.Add a line that loads the Semantic MediaWiki extension.    wfLoadExtension( 'SemanticMediaWiki' );Add another line that enables semantics using the domain wiki.opensourceecology.org.    enableSemantics( 'wiki.opensourceecology.org' );STEP 2 – Update the Wiki DatabaseFrom the MediaWiki root directory, run the MediaWiki maintenance update script. This updates the database to support the new extension.    php maintenance/update.phpThen run the Semantic MediaWiki setup store script. This prepares the semantic data storage system and is required for queries to function.    php extensions/SemanticMediaWiki/maintenance/setupStore.phpSTEP 3 – Install Semantic Result Formats From the MediaWiki root directory, run the Composer command to install Semantic Result Formats.    composer require mediawiki/semantic-result-formatsThen open LocalSettings.php again and add a line that loads the Semantic Result Formats extension.    wfLoadExtension( 'SemanticResultFormats' );After adding it, run the MediaWiki maintenance update script again.    php maintenance/update.phpSTEP 4 – Install Page FormsFrom the MediaWiki root directory, run the Composer command to install Page Forms.    composer require mediawiki/page-formsOpen LocalSettings.php and add a line that loads the Page Forms extension.    wfLoadExtension( 'PageForms' );Run the MediaWiki maintenance update script again.    php maintenance/update.phpSTEP 5 – Verify InstallationVisit the Special:Version page and confirm that Semantic MediaWiki appears in the extension list.    https://wiki.opensourceecology.org/wiki/Special:VersionIf possible, create a test page and attempt to run a simple semantic query to verify the extension is working correctly.    {{#ask: }}If this renders output instead of raw text, Semantic MediaWiki is working correctly.  

WHY THIS IS IMPORTANT

Installing these extensions will allow us to:• Standardize all GVCS project pages • Automatically generate project index and navigation pages • Reduce manual maintenance work • Improve long-term wiki sustainability • Make editing easier for contributors • Prevent duplicate or outdated information

These extensions are widely used, actively maintained, and considered stable for MediaWiki installations.I’m happy to assist with testing or validation after installation.Thank you very much for your help, and please let me know if you have any questions or concerns.

To Your Success, Steven