wiki:WikiStart

Version 6 (modified by Thanatermesis, 16 years ago) ( diff )

--

Table of Contents

  1. How to be a Good Bug Buster (beta-tester)
      1. What? Why?
      2. Environment
      3. Unimaginable Possibilities
      4. Biggest Headaches
      5. Combinations
      6. Frequent Problems in applications
      7. Betatest yourself
      8. Other different types of bugs
        1. Pebkac
        2. Wording
        3. User Experience (UX)
      9. Remember
    1. What is
    2. Dependencies
    3. Hands on !
    4. Time to build the package !
    5. Final points
    6. Interesting Links and more Info
  3. Development with EFL and tips & tricks
    1. Introduction to EFL
    2. Learning EFL
    3. E17 Modules
      1. Some Tips & Tricks
    4. Misc
    5. Notes
  4. A list of programming techniques
    1. Programming Procedure
    2. States
    3. Special Situations
    4. Integration
    5. Checks
    6. Human factors
      1. Memory
      2. Visual Readability
      3. Visual Blocks
      4. Think less
    7. Convention Names
      1. Never create names like this
      2. The good way
      3. The optimal way
      4. Big Applications
    8. 7+1 rules for names that must-read from …
    9. The 5 steps coding procedure
    10. Wisdom
        1. Common Excuses For A Software Rewrite
        2. Why Rewriting Is (Almost) Never A Good Idea
      2. The Zen of Python
      3. Art of Unix programming
    11. Extra
  5. How to make a Mirror for Elive
      1. Requirements & Notes
      2. FAST INSTRUCTIONS
  6. How to use SVN
    1. Basic Usage
    2. For developers
    3. For Administrators and Servers
      1. More information about SVN
  7. How to make Translations in Elive
    1. Requirements
    2. What can I translate ?
    3. Important things to Know
    4. English Proofreadings
    5. Tips
    6. Control
    8. Error: Page WhyToPay does not exist

Welcome!

New Website

This Website has totally changed!

The idea of this website now is that to automatically create accounts to the collaborator users (see the form in elivecd.org) so they can be directly involved in the project

Ideas

This website want's to work on this way (Actual idea):

  • Anonymous users (any user without login)
  • Authenticated users (any user with an automatic account created from the form of Collaborators in the Elive website)
  • Developer users (users that requests a SVN access)
    • SVN: RW (it is managed by groups, so it will be have access to the things that he will want to have)
      • Note: This developer users are a bit tricky thing... if this website is mean to a place where the users want to collaborate and feel involved directly, they can't do anything (modify the source code, with bugfixes or features) unless they request to be on this group and to have these permissions.
        • How they will send any patch or something like that if they can't have access to the SVN ? we should need to found a way, a way that they send a patch or something like that and that we know about it, a system for that
    • Milestone/Roadmap: RW ?

Completed ?

No, I have not finished to set up this website yet, Im brainstorming basically about which permissions to give to them, also is possible to create groups... Ideas ? Suggeriments ? please enter in #elive-dev and give us your ideas !

Old Website

The old website is totally removed, there's nothing interesting on it (except a few howtos), by other side the svn repository still working (will be cleaned up in the future)

Thanatermesis

Note: See TracWiki for help on using the wiki.