File:  [NetBSD Developer Wiki] / wikisrc / users / jdf.mdwn
Revision 1.9: download - view: text, annotated - select for diffs
Sat Dec 22 13:19:16 2012 UTC (5 years, 4 months ago) by jdf
Branches: MAIN
CVS tags: HEAD
Even more cosmetics.

    1: [[!toc levels=2 ]]
    2: 
    3: # jdf's wiki page
    4: 
    5: Note: This is not what I'm really working on, it's just a place to gather some 
    6: notes I took about some topics.
    7: 
    8: ## NetBSD flavoured
    9: 
   10: Currently, NetBSD is a very generic operating system, leaving almost all
   11: choices up to the user. While some consider this a strength, and it
   12: definetly is for people who know what they're doing, it's an obstacle for
   13: people who then have to setup *everything* by hand.
   14: 
   15: Creating a *NetBSD flavoured* distribution shouldn't be much work, and require 
   16: just minor sysinst modifications.
   17: It shouldn't be much work to just package distribution sets that already
   18: include a list of packages it installs and several preconfigured configuration
   19: files, maybe also some additional wrapper scripts.
   20: On the other hand, you could also add some package calls to sysinst and just 
   21: provide a list of packages you consider necessary.
   22: 
   23: My original attempt was to create a range of distributions for different 
   24: purposes, i.e. one for developers, one for graphic designers, one for servers, 
   25: etc. I don't know if this is the right way, esp. since some of the applications 
   26: are *very* specific. You cannot really provide a sane server default 
   27: installation except for some basic things like installing a vim, but that's all.
   28: My current idea is to provide just one, maybe named *NetBSD flavoured*, with at 
   29: least the following tools on board:
   30: 
   31:  * vim
   32:  * pkgin
   33:  * git
   34:  * fossil
   35:  * subversion
   36:  * some other important VCSes
   37:  * light-desktop (i.e., LXDE)
   38:  * screen (tmux is in base)
   39:  * some sane X terminal emulators
   40:  * a browser (Firefox?!)
   41:  * a mailer (Thunderbird? Claws-mail?)
   42:  * emacs (maybe too large?)
   43:  * perl
   44:  * python
   45:  * mplayer (when it's possible to pack it up)
   46:  * pdf viewer
   47:  * preconfigured bozohttpd running on localhost showing documentation
   48: 
   49: ## NetBSD documentation
   50: 
   51: In [this 
   52: post](http://mail-index.netbsd.org/netbsd-docs/2012/09/20/msg000295.html)
   53: I shared some ideas about what to do with documentation. Though much of it 
   54: was proven not practical by the replies, I still have one idea: Unify 
   55: documentation of NetBSD, and provide it all on a NetBSD system.
   56: 
   57: The first step is to merge as much content as possible into the NetBSD wiki. 
   58: Currently, the NetBSD documentation is very diverse in its distribution form.
   59: 
   60: Then, the Google Code-In produced some nice results, including a CGI for a small 
   61: markdown wiki to browse the wiki (if it was offline), and maybe even a terminal 
   62: markdown browser.
   63: 
   64: Finally, ship these two in a pkgsrc package or even with base, and provide a 
   65: small script which regularly updates the documentation.
   66: 
   67: ## NetBSD website
   68: 
   69: Currently, the NetBSD website is written in HTML and Docbook and requires many 
   70: tools to be edited and committed. The final goal should be to have just a small 
   71: homepage with a bit important information, but all the essential technical 
   72: information should be in the wiki. There's also a separate page for this: 
   73: [[htdocs_migration]].
   74: 
   75: Though the plan is currently to migrate *all* contents to the wiki, I don't 
   76: think this is the way to go. A wiki just doesn't leave a good impression.
   77: 
   78: ## NetBSD community and marketing
   79: 
   80: Just some thoughts... I think NetBSD has a very bad way of making technical 
   81: ecisions which are counterproductive from a marketing point of view, or just are 
   82: not used for marketing purposes.
   83: 
   84: The world has changed; nowadays, there's a growing *hacker community* which 
   85: consists of many people with an age below 30. They're just not used to the 
   86: flexibility of the old tools Unix provides, and to the flexibility you have 
   87: with a modern Linux.
   88: 
   89: There are repeating questions why NetBSD doesn't use git as its primary VCS, but 
   90: rather CVS. CVS *is* indeed a very mighty tool, but many people don't know. They 
   91: like git more because they can explicitly `push` with it (and don't know about 
   92: hooks in CVS or Subversion).
   93: The same holds for many other decisions.
   94: 
   95: NetBSD has a very... oldish view of how a community should be organised. On the 
   96: one hand, there are the developers, which are coding the project, maintaining 
   97: the website, maintaining packages, maintaining documentation, organising events, 
   98: organising NetBSD itself... and on the other hand, there are the users. They're 
   99: rather consumers than contributors.
  100: 
  101: The few ones which want to contribute are doing so, and after some time becoming 
  102: developers with the right and possibility to do everything, but there's nothing
  103: in between. There's only few community involvement overall, though there are
  104: many topics which don't require a developer status.
  105: I think breaking with the old habits and providing more community involvement 
  106: and community support is the way to go, but except for starting with a 
  107: user-editable wiki, I don't have many ideas how to do so.
  108: 
  109: ## NetBSD current
  110: 
  111: The same problem exists imho with the release cycle. The standard release cycle 
  112: of NetBSD is too slow for many people who use it privately (just see how 
  113: wide-distributed Arch Linux got), and tracking current is a rather obscure thing 
  114: with compiling things on your own, etc. ...
  115: And it's not well-documented. There *are* changes, but who knows them? Which was 
  116: the current version where tmux was imported? Etc.
  117: 
  118: Tracking these changes more centrally, and providing a nice way to install and 
  119: track a current installation would be a great benefit for NetBSD.

CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb