User:CityK: Difference between revisions
m (fixed link) |
m (note to self) |
||
| Line 440: | Line 440: | ||
| '''<span class="plainlinks">[[Technical Background & Developer Page|Developer Section]]</span>'''<br /><small>Information to help device driver development |
| '''<span class="plainlinks">[[Technical Background & Developer Page|Developer Section]]</span>'''<br /><small>Information to help device driver development |
||
|} |
|} |
||
-------- |
|||
Works: [{{SERVER}}{{localurl:Special:Allpages|{{ns:100}}}} {{ns:100}}] |
|||
Doesn't work: {{Note|[{{SERVER}}{{localurl:Special:Allpages|{{ns:100}}}} {{ns:100}}]}} ... stupid wiki. |
|||
also see http://www.mediawiki.org/wiki/Plainlinks |
|||
Revision as of 22:48, 31 May 2009
This is my sandbox. Being a sandbox, everything you see here is a work in progress. However, my intention should be pretty clear from the content.
But if my intention isn't clear, here's what I propose:
- Unification of the v4L and DVB wikis
Why?
- avoid duplication of effort (inter-duplication), more efficient
- one stop shop
- more user friendly, more inviting, and hopefully spawn more interest
- (I also have a good idea in mind about a linuxtv website face-lift/redesign ... and it would be easy to bring about a common branding to both the website and wiki ... but first things first -- the wiki)
Things that would have to be accounted for:
- User Accounts / Log-ons
- Exporting article History and discussions -- would want to preserve as much as possible
- Duplicate article names i.e. Hauppauge on v4l and Hauppauge on DVB (actually, I don't think that this would be too difficult a problem -- i.e. just apply a v4l tag on duplicates before moving then over and then merge the two articles later)
- time and assistance to perform the merge
Features to incorporate into the "new" wiki
- more info (beyond supported devices -- spawns interest in new projects?)
- unified look and feel and "branding" (e.g. "wikitables" in the wiki articles; graphic for website and wiki (I have, what I believe to be, a good idea in mind already)
- new features like:
- sortable tables,
- a news section on the front page (for quick dissemenation of latest v4l-dvb kernel updates/patches etc, important m/l discussions, new hardware spotted announcements, newly supported hardware announcements)
- start using "this article is a stub", "this article needs expanding" blah blah blah type headers (just like on Wikipedia and elsewhere)
Some things about the wiki that I feel are now needed
- Active co-ordination / oversight ... the wiki's are slowly reaching critical mass ... need a dedicated team to check that new submissions are correct or placed in right place and are "up to par/standards"
- perhaps a mailing list regarding the wiki ? -- it would help with decision making
- Formalize entries
- this includes proper article naming .... more then slightly pedantic, but necessary (think libraries -- they don't just throw things on shelves)
- reduce/clean out "first person" commentary and questions in articles
- Reduce subject fragmentation (i.e. where a single subject matter is needlessly broken into multiple articles)-- common problem
- Reduce (intra-) duplication (i.e. where multiple articles conveying the same thing have been created) -- common problem --> all the USB articles were an example of this insanity
- lots and lots of updating
And now, without any further adu, here's a preliminary mockup I have put together of a unified wiki:
- you'll currently find a lot of placeholder text (i.e "Applications to watch TV * TV Viewing * TV Recording"), but that's all it is -- I've simply kept the v4l links there for placement purposes and as reminders of stuff needing attention if things are to be merged... the final draft would of course remove such items and be more clean
- some of the layout is not clean...I just ran out of patience with futzing about with tables etc and just want to present the idea/proposal...this can all be cleaned up and become more presentable later on
Wiki Main Page:
Welcome to the LinuxTV Wiki !
|
This wiki is intended to become an authoritative source of information regarding the use of analog video and digital TV sources under Linux -- i.e. the subject matters covered under the LinuxTV umbrella/framework. The basic plan is to aggregate information about: available hardware; how v4l or dvb work; software used with the hardware and so forth. Like all other wikis, the LinuxTV wiki relies upon the contributions of its users. Hence, it will only be as useful as we make it! So we encourage you to share your knowledge and help with the task of turning this site into a repository of knowledge. Your input (whether it be by providing a set of instructions for how to get a certain device working; a minor improvement to an existing article; or an explanation for some complex concept) will be highly appreciated. -- The LinuxTV WikiTeam [People behind V4L] |
|
|
User Sign up /Login Subpage:
A Few Notes Before you Begin
Before you jump in and make your contribution, please first familiarize yourself with the layout of the site. Doing so will help you to place your information in the right location. As the wiki grows, it takes an increasing amount of effort and discipline to keep it from quickly turning into a tangled mess. So it's up to each of us to make sure the information submitted is easy for everybody to find and access.
If you make a contibution and later find that your submission has been edited or moved to another area of the wiki, please don't feel offended. Everyone understands and appreciates the time and efforts you took, but bear in mind that a factual and well-organized resource for everyone interested in analog or digital TV is the ultimate aim of the LinuxTV wiki.
Submitters should also know that, to keep the information contained in the wiki free, all contributions are automatically licensed under the GNU General Public License GPL. If you wish, you may specify in each case that your contribution is dual-licensed under the MIT License. Please do not reproduce or submit copyrighted works without obtaining the express consent of the owner or its agent.
Lastly, to help keep the wiki free from spam, contributors are required to set up an account and to sign in before they can post to the wiki. (This is a painless process that only takes a few seconds). To sign up an
Now enjoy and have fun! -- The LinuxTV WikiTeam [People behind V4L]
User Info Page:
|
|
|
Hardware & Components Page:
|
|
||
|
|
... is this section even necessary ?? |
Sub pages:
|
Analog Devices Video via PCI
Video via PCI Express
Video via USB
Video via PC104
Graphics cards with TV Tuner and/or Capture facilities Other devices |
DVB Pre-configured Systems and Set Top Hardware |
Technical Background & Developers Page 
:
|
|
|
Misc Info & ideas for me:
Icons wanted:
- need to find or create a chain link icon for "links"
- * terrestrial broadcast tower
- sat dish
- * pcmcia
- pci
- pcie
- firewire
Colours
- v4l --> style="background-color:#006600;
- DVB --> style="background-color:#6289AB;
Stupid templates
The "click" way:
| Template:Click | User info How to install your hardware, and software to use it with |
Template:Click | Hardware & Components Information on Hardware devices and related components |
| Template:Click | Technical Background Technical details, standards, etc |
Template:Click | Developer Section Information to help device driver development |
The "Extention:ImageMap" way:
| <imagemap>Image:User_Info_icon.png|48x48px
rect 0 0 50 50 User info desc none</imagemap> |
User info How to install your hardware, and software to use it with |
<imagemap>Image:Hardware_icon.png|48x48px
rect 0 0 50 50 Hardware & Components desc none</imagemap> |
Hardware & Components Information on Hardware devices and related components |
| <imagemap>Image:Technical_background_icon.png|48x48px
rect 0 0 50 50 Technical Background & Developer Page desc none</imagemap> |
Technical Background Technical details, standards, etc |
<imagemap>Image:Developer_icon.png|48x48px
rect 0 0 50 50 Technical Background & Developer Page desc none</imagemap> |
Developer Section Information to help device driver development |
Works: Archived
Doesn't work:
... stupid wiki.