| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

7a – What Is To Be Done

Page history last edited by Sujith Prathap 13 years, 2 months ago

 

Here's a place where members of the Co-Editor Team can plan, plot, discuss, debate, and so on about improving our NI FAQ Wiki, with the newest items being added at the top of the page (reverse chronological order).  

NB: Please feel free to sign & date your contributions ('fraid there's no auto-sig function, so please tap in your sig manually, eg: - dalinian 07:00 UTC 08 Jan 11




CO-EDITOR TEAM DISCUSSIONS (12 Jan 11 – The Future)

 

 

Notion Ink – FAQ Wiki Co-Editors: the Google Group communications hub

Since inter-Co-Editor communications were becoming a little cumbersome on the Wiki itself, François has kindly suggested and set up a mailing list for us at Google Groups, which actually means we have a group communications website:

Google Groups
Notion Ink – FAQ Wiki Co-Editors
Visit our group

 

Here's hoping we'll get familiar with talking about enhancing and expanding our NI FAQ Wiki using the facilities of our new Google Group communications hub. - dalinian 19:50 UTC 12 Jan 11

 

Using our new Google Group communications hub INSTEAD of this '7a – What Is To Be Done' Page

  • I tried to send email to the address and yahoo rejected it. – Lee cx650t on 13 Jan 2011 at 7:02 UTC
  • Hmmm... which address, I wonder? There are TWO ways to use our new Google Group communications hub:
    1. As a website: easiest, IMO – just go to http://groups.google.com/group/nifaq (recommendation: bookmark this page for quick access in the future); using the [+ new post] button or a 'Reply' link lets you post your message in the right place, and puts it in all Co-Editor's email inboxes (if they're choosing to get messages this way)
    2. As a mailing list: easy too – a message sent to nifaq@googlegroups.com shows up on http://groups.google.com/group/nifaq and in all Co-Editor's email inboxes (if they're choosing to get messages this way)
    • - dalinian 19:05 UTC 13 Jan 11
  • PROBLEM SOLVED in the meantime (mail to the list has to be sent using the registered address only) - Francois Brutsch 10:50 UTC 14 Jan 11 
  •  I tried to send email to the address and yahoo rejected it. Here's what I wanted to say...
    • Greetings... I discovered something today while searching for the FAQ on my i1 phone. Do a search on Google for NIFAQ and take a read at what comes up. Learn something new everyday... Maybe need to change the site name slightly...
    • –  Lee cx650t on 13 Jan 2011 at 7:02 UTC
    • Yeah, I was keeping schtum on that, having discovered it myself a while ago; just an unfortunate coincidence, IMO. Googling 'ni faq' finds you info on Northern Ireland, National Instruments, et al; but Googling 'ni faq wiki' finds you US, HERE! - dalinian 19:40 UTC 13 Jan 11
  • Info from 'POLL' on this page and 'Insert Polls' from page '7d – Wiki Editing Tips-n-Tricks' (both by Lee) copied to message 'Adding an associated Poll to a Wiki page' on our new Google Group communications hub. - dalinian 19:50 UTC 13 Jan 11

 

 



CO-EDITOR TEAM DISCUSSIONS (24 Dec 10 – 12 Jan 11)

 


New Content (11 Jan 11)

 


Android 3.0 (Honeycomb)

  • There was a recent CES interview where Rohan specifically said they would support Honeycomb given ADAM meets the minimum requirements.  He doesn't know what they are and there has been no clarification as to minimum screen size requirements.  All of the articles about no hardware requirements stem from the same tweet from an android developer that only mentioned no 'hard CPU' requirement.  Unless someone has seen otherwise, section 3a iv Will there be support for Android 3.0 (Honeycomb) when it is launched by Google? should be updated to reflect that. - phazei 8:05 GMT 11 Jan 2011
  • With respect, my feeling is that this whole 'minimum screen size requirement' for Android 3.0 (Honeycomb) "controversy" is a red herring with regard to ADAM. AFAIK, it's logical to infer that Google want Android 3.0 (Honeycomb) on as many tablets as possible, from as many tablet manufacturers as possible, and as soon as possible in 2011 – from 7-inchers (800x480px - 1024x600px), through 10-inchers (1024x600px - 1280x800px), to even larger touchscreens. Although the only 'Android Honeycomb 3.0 full-live demo!' to date involved a 1280x800px Motorola Xoom <- CAUTIONpromo includes yet another 'Americans slaughtering each other with guns' Hollywood "entertainment", despite last week's real life Tucson massacre, in the absence of any hard evidence that ADAM fails to meet a Google-imposed 'minimum screen size requirement' for Android 3.0 (Honeycomb), then I'm content to believe Rohan's assertion that NI will post a user-installable ADAM upgrade to Android 3.0 (Honeycomb) in mid-2011. - dalinian 13:40 UTC 11 Jan 11

 

 


Vacancy and NIH Disaffiliation Proposal

 

The “Andy 'NIH' Smith” problem

Over at NotionAddicts, the mod team are discussing ‘Peace-making and Community-building: the “Andy 'NIH' Smith” problem’ in the mods-only Situation Room, with a view to open discussion in the ‘NotionAddicts Problems and Questions’ forum. Turns out that, judging by his unethical actions and foul-mouthed reaction to constructive criticism, Andy is a rather unsavoury character, garnering such comments from other mods as:

  • “Andy has attempted attacking, attempting to divide, spreading rumors, "posting" under many aliases”
  • “narcissistic, disrespectful, immature, and unethical (to name a few)”
  • “somewhat of a troll”
  • “I am speechless from Andy's response” 

Andy's self-image at NIH

 In a PM to Andy at his NotionInkHacks (NIH) website, I asked if he would like to remain on our Wiki Co-Editor Team:

“Three days ago, in an email conversation initiated by you (subject: Pixel Qi), I encouraged your active participation in our NI FAQ Wiki by suggesting three simple actions you could take. AFAIK, not only have you done none of them, but you've in fact been a Co-Editor in name only, never having actually edited anything on the Wiki. So we've downgraded your Access Level to Writer. Unless you're prepared to overcome your well-evidenced sectarianism and participate at the Wiki, we'll be obliged to cancel your workspace rights completely (although you'll still be welcome to browse the Wiki), and recruit an enthusiastic Co-Editor volunteer to replace you.Please let me know if you intend to be an active participant at the Wiki.

The relevant part of Andy’s reply reads:

“At the end of the day in just a few weeks the news will be out and that WIKI will be old news. Take my link down, talk trash, but stop bothering me as I don't have time for it and I am done playing kiss ass. [...] I would really prefer it if you refrained from contacting me from here on out. I am kind of sick of talking to you and I am not out to be your friend anymore.”

Phew! I think we can take that as a “No”, then. Personally, I see our NI FAQ Wiki going from strength to strength, both right now and for the foreseeable future.

 

Co-Editor Vacancy

So, we have a 7e1 – Vacancy for an enthusiastic Co-Editor volunteer, and I’m offering it initially to NotionAddict phazei, who not only recommended us to PBworks in the first place, but who has posted several times to our ‘Call Out to join our 'Notion Ink FAQ' Co-Editor Team’ thread, from post #6 onwards. If you know of anybody else who you believe would make an enthusiastic Co-Editor volunteer, do please post a suggestion here.

  • Sorted! Welcome to our new newest Co-Editor Phazei, who has taken over the 1st §7e page at 7e1 – Phazei - dalinian 01:45 GMT 05 Jan 11
  • Hi! - phazei 11:03 GMT 07 Jan 11

 

NIH Disaffiliation Proposal

The more we’ve discovered about NIH, the more it seems to reflect the dark side of Andy’s personality, in design and temperament, focussing on elitism/secrecy/sectarianism/"Possible Monetary gain" – see, eg: ‘Would you like to join the A-Team?’ – which IMO doesn't sit well with the bright sided egalitarianism/openness/community-building/gift-economy ethos of the rest of the NI community, including NotionAddicts and our NI FAQ Wiki. While people with accounts at NIH are welcome to be NI FAQ Co-Editors, I’m not sure any still are, so I think saying on our NI FAQ Front Page that we’re a collaborative enterprise by members of NotionAddictsand NotionInkHacks is no longer true. I propose we change that to a collaborative enterprise by members of NotionAddicts and the NI community, and remove the NIH masthead from our animated NI FAQ Wiki masthead. Any objections?

dalinian 17:50 GMT 04 Jan 11

  • How about "a collaborative entreprise of member of the NI community, which originated in the NotionAddicts forum"? To keep the ecosystem both simple and fluid, it seems to me better to see the various - interconnected - elements as independant: NotionAddicts core is the forum, the FAQ wiki or, for that matter, the mapping of the ADAM community, are two other elements which should live their own life. -Francois Brutsch 19:30 04 Jan 11
  • Yep, I like it Francois, and I'd concentrate it to a collaborative enterprise by members of the NI community, originating from NotionAddicts - dalinian 22:40 GMT 04 Jan 11
  • Sorted! As you can see on our NI FAQ Front Page:
    • strap line is now  A product of participation – collaborative enterprise by members of the NI community, originating from NotionAddicts
    • animated NI FAQ Wiki masthead frame 4 now name-checks Rahul's original FAQ blog posting: 

    • dalinian 01:45 GMT 05 Jan 11
  • Great Work !! :D - sujith GMT 2:32 05 Jan 11
  • Found a reference to Notion Ink Hacks in 1f – OS Alternatives . I am removing Notion Ink Hacks from there as well - sujith 08:20 11 Jan 11

 


Mailing list / Googlegroup?

  • As this Wiki is growing beautifully, I think there is a need for better communications between co-editors. Our individual co-editor page or this What Is To Be Done page are too dependent on everybody checking them. I feel also they might be sometime embarrassing as they are in full view of all the visitors (e.g. discussing Andy NIH). From my experience of other similar collaborative groups, I would suggest having a very simple mailing list between all the co-editors. E.g. today I had a problem of embedded videos that I would have liked to raise, but I could only do it quickly with dalinian since we are both on Skype; and he put something about it here to ask if any co-editor has an idea, but I don't know if anybody saw it yet?
    A Googlegroup would be easy to set up, can be kept private, and we can individually set if we want to get every email immediately, or a list once a day, or not at all and look on the web. Of course we wouldn't need to email about every normal editing here, but it would be useful in my view for discussions or problems.
    - Francois Brutsch 00:35 UTC 09 Jan 11 
  • Thanks for the ‘Mailing list / Googlegroup’ suggestion, Francois, and it gets my wholehearted SUPPORT, for all the good arguments in favour which you advance. Would any of our Co-Editor team like to Block, Stand Aside, have Reservations, or Not Support this proposal?
    • Non-support: "I don't see the need for this, but I'll go along with the group."
    • Reservations: "I think this may be a mistake, but I can live with it."
    • Standing Aside: "I personally can't do this, but I won't stop others from doing it."
    • Blocking: "I cannot support this or allow the group to support this. It is immoral."
      ~ from ‘Activism: Peace: NVCD: Consensus Process
    • - dalinian 12:30 UTC 09 Jan 11
  • I think this is a good way to reduce the clutter that I anticipate for when users actually get the device. You have my support :) - Rahul 15:41 UTC 09 Jan 11 
  • I already get emails anytime the wiki is modified. Based on the modification emails I get it appears that only four or five of us are doing anything. ;>
  • Is there a way to make part of the wiki "eyes only"?  If that's possible we could also link to / add Tim's map and other "owner specific" information which only "authorized" folks could view. cx650t on 10 Jan 2011 at 06:58 UTC.
  • Googlegroup created, every co-editor has normally received an email with the address to send a message to all co-editors and the URL of the group (visible only for members) - Francois Brutsch 22:00 UTC 11 Jan 11

 


Animations

  • Is there a way to slow down the speed at which the images are displayed? e.g. on the front page I feel that the images flash by too quickly to take in what is being shown. – cx650t 23:00 UTC 7 Jan 2011
    • Yep, I've slowed the animation rate for the NI FAQ Front Page graphic, nominally to 10 seconds/frame. - dalinian 15:15 UTC 08 Jan 11
  • I also really like a lot of the animations being installed in the Glossary. Way to go. – cx650t 23:00 UTC 7 Jan 2011
    • Mmmm, me too – so I made another, for the App entry. I'm using the quick-&-easy-to-use, free, online 'Animated GIF Generator Tool' at image-tools.com – and your invited to use it too, where multiple images will work better than just one. - dalinian 15:15 UTC 08 Jan 11
    • Through circuitous means, I've also made an animated GIF version of NI's Genesis promo SWF and added it to the App Store and Genesis entries in the Glossary, and to the What is Genesis? answer. In part this involved using the very handy Video Converter called BenderConverter which facilitates video to animated GIF conversion. - dalinian 07:00 UTC 08 Jan 11
  • Well, as one who is not overly keen on animations, I'm at least grateful that they are slower! ;) - Francois Brutsch 00:20 UTC 09 Jan 11 

 


Glossary

  • What about adding a glossary for the disambiguation of abbreviations? I read one comment, where a reader was asking about WSVGA and IPS. The addition of a glossary would surely be beneficial to people who are unaware of technical terms. 
    • -sujith  09:30 GMT 31 Dec 10 
  • Superb ideasujith – here we go: 1e – Glossary – please start filling her up, cross-linking to relevant NI FAQ Wiki pages where appropriate. I've done page footer integration, but left it out of the NI FAQ Front Page Table of Contents and the SideBar while it's still "under construction". When the Glossary is ready for public consumption, please add appropriate links to the NI FAQ Front Page Table of Contents and the SideBar. Assuming that you'd like to be Glossary Project Lead, please add a section of that name to your 7e10 – Sujith Prathap Conversation Page, in the Project Conversations zone, so we can address messages about the Glossary to you there. 
    • dalinian 10:00 31 Dec 10
  • Page is now 1g – Glossary after §1 page resequencing from 1e to 1g. I think it's good to go for public consumption, so I have added it to the NI FAQ Front Page Table of Contents and the SideBar.
    • dalinian 15:29 GMT 02 Jan 11
  • How about italicising all ADAM related info in the explanation column, to allow users to easily read how the term is used in the context of the ADAM?
    • -sujith 16:35 GMT 05 Jan 11 
  • Yep, saw where you were going with this, liked it, and developed your idea further into a major Systematising Revision 1, now expedited and documented below the Glossary Table.
    • I've left quite a few placeholders in RedBoldItalicCamelCase behind which need replacing with appropriate content, and so if any Co-Editor would like to lend a handby all means enhance and expand our lovely 1g – Glossary
    • Now we have a well-populated 1g – Glossary we can help out Wiki users by linking to it from substantive Wiki pages; for instance, here's a line from2b – System-on-Chip:
      • ADAM's computing power derives from an nVidia Tegra 250 SoC, which has dual-core ARM Cortex-A9 MPCore CPUs. It also has an Ultra Low Power GPU.
      • That's 7 links to our 1g – Glossary in one sentence! So a non-techy Wiki user can find out more about those 7 items by linking to their entries on our 1g – Glossary
      • The more familiar you are with our 1g – Glossary, then the more likely you'll be able to add Glossary links like these to substantive Wiki pages.
    • dalinian 17:45 GMT 06 Jan 11
  • On the glossary page I don't think we need to preface each acronym with an alphabetic header. As the list continues to grow, why not just let the table list everything. I believe folks will quickly figure out how to scroll it to locate the term they are looking for. - CX650t.
    • One of the banes of the computing industry for the non-techy consumer are the multitude of TLAs – Three Letter Acronyms. I think the way we show both the abbreviation in the Term column (eg: EDR) AND what it stands for in the Expansion column (eg: Enhanced Data Rate) helps the non-techy consumer get up to speed with some of the technicalities that some of us are already more familiar with. - dalinian 18:05 GMT 06 Jan 11 (Agreed - cx650t 06:15 UTC 07 Jan 11)
    • Another advantage is the 'Table of Contents', which references each 'Heading 4' item in the Term column. It's becoming as much a 7c – Standard Page Element at the top of each Wiki page as the nav-aid tripartite box is at the foot of each Wiki page. Now that the microGraphics have spread the table out down the page, I think the 'quick reference guide' provided by the ToC adds value to term-seeking.
      • This is just a Glossary and doesn't need a "table of contents" The contents are the information and there isn't any need to list everything twice. Since links in the various pages can link straight back to the applicable cell, and ALL of the TLAs are/will be listed on the page, I feel that the long list at the top of the page just clutters up the document. - cx650t 06:15 UTC 07 Jan 11
      • Yeah, I take your point, so I've made a 'Heading 1 only' ToC ABOVE the Glossary Table (only three lines long), moved the 'Headings 1-4' Toc BELOW the Glossary Table, and headed it 'Quick Reference: Glossary Terms - a Table of Contents'. It's extremely useful to check that ALL items in the in the Term column are properly 'Heading 4' tagged (because often new ones aren't, eg: FM, IPS TFT). Tagging your new items in the in the Term column as 'Heading 4' means that:
        • (1) they show up in the 'Quick Reference: Glossary Terms - a Table of Contents' and
        • (2) it's easy to get their link code for links in the substantive Wiki pages – just right click on the he 'Quick Reference: Glossary Terms - a Table of Contents' entry and click on 'Copy Link Location' or similar
      • dalinian 17:20 GMT 07 Jan 11
    • It's also worth bearing in mind that many calls to the 1g – Glossary will come from in-line links in the body text of substantive Wiki pages, which jump straight to the relevant term in the Glossary Table. - dalinian 18:05 GMT 06 Jan 11
  • Thanks for providing the instructions for inserting additional table cells. (cx650t 06:15 UTC 07 Jan 11)
    • Which is: 
    • EDIT tab > click in a cell of the Glossary Table > [ Table ∇ ] pull-down menu > Row > { Insert row before | Insert row after }
    • - dalinian 17:45 GMT 07 Jan 11 
  • Just thought of a format which derives from dalinian's modification with a simple change.

PQ

Pixel Qi Corporation

<Explanation>

Pixel Qi is an enterprise founded by Mary Lou Jepsenwho was involved in the development of low-power displays she invented originally for the OLPC (One Laptop Per Child) XO.

<space>

<How it is used in the ADAM(italicised) >

• ADAM offers a Pixel Qi transflective display that allows users to read the screen under bright sunlight as an alternative to the standard LCD display.

2e – Display

Pixel Qi

on Wikipedia

Pixel Qi

website

    • IMO italicising ADAM relevant content would help readers who know what a term means and are looking only for information of how a particular concept/feature is used in the ADAM. -sujith 16:49 GMT 07 Jan 2011.
    • I like that idea, sujith – feel free to make it so, and I'll modify the 'Explanation column – text only, cross-linking to Terms' in 'Systematising Revision 1' to reflect this update. - dalinian 17:45 GMT 07 Jan 11
    • Done! The contextualising lines are all in bulleted • italics, and the 'Systematising Revision 1' re-write describes content and formatting for the whole Glossary Table - dalinian 13:45 GMT 08 Jan 11

Wiki Contents

  • I was discussing this FAQ with a couple of other WEB designers at work and felt like there's an information overload. This isn't a replacement for the manual. I took it as a source of answers for all of the questions raised on the Wordpress Blog and others and to augment the information displayed on the NI pages. (Or clarify some of the NI information due to language barriers) (cx650t 06:15 UTC 07 Jan 11)
  • Was also thinking that using the linking provided by the WEB, that we should have a "photo" page where all of the photos could be viewed / replaced / updated. Then where the Wiki pages required / would be enhanced by embedding a photo, the photo would be "linked" back to the photo page. A newer "better" image could be posted to the photo page which would then ensure that all the in-line images would get updated at the same time.  We could do the same for all of the various videos. By placing the videos "on-site" we wouldn't need to worry about broken links when the videos on You Tube vanish or are replaced too. (cx650t 06:15 UTC 07 Jan 11)
  • Also one thing that really bugs me about all of the various Forums / Wikis is "stale" information. If a question has been asked and answered then the entire thought stream should be condensed down to the question and the correct answer. e.g. all of the conjecture and photos of the prototype should be removed or prominently flagged as such. Nothing worse than to look up an answer to a question and find answers for the version of software/hardware multiple versions older than the one you are asking about. It also removes all the folks answers (which are wrong) thus streamlining the whole process.  Unfortunately until one of us actually gets an ADAM most of our work is pure conjecture. Reminds me of the focus group of four graduate students discussing a device in the center of the conference room table. The physicist wants to know what makes it tick. The mathematician wants to know the theory of its operation. The biologist wants to know if it can reproduce. The Liberal Arts grad student wants to know if everyone wants fries with their burgers... ;>  cx650t on 11 Jan 2011 at 05:55 UTC.

 


Change Management & Wish List

  • Where do we post suggestions / how do "we" approve pages. Right now it appears that any of us can change any page "willy nilly". I like that Tim is taking the lead on standardization / standardisation. Any thought as to a "voting" page for changes? e.g. make a recommendation and if the majority agrees, then the change is posted to the overall page organization / content?  
    • I'd like to add a "Wish List" to section 6 (as that seems to be the best place currently) to gauge users requests and to provide Rohan et al with "free" market research. To continue with the development of the ADAM and future "EVE"...
    • Lee 11:26 GMT 05 Jan 11
  • PBworks does away with the 'Talk' page tab seen in MediaWiki, so we're using this 7a – What Is To Be Done page for inter-Co-Editor conversations, as well as having one-to-one conversations on each others Co-Editor Conversation pages, eg: 7e5 – Lee (cx650t). Since we're a well-motivated group of NotionAddicts, I'm trusting that generally any change made will be a good one, so there's no need for even an informal approval process, let alone voting. So if any Co-Editor perceives an enhancement or expansion that would improve our Wiki, they're welcome to take the initiative, jump right in, and edit the page(s), thereby expediting that improvement straight away.
    • I like the "Wish List" idea a lot, but §6 is for "issues related to third-party apps, hardware, and accessories." Since a "Wish List" crystallises the collective desires of our 1d – Notion Ink Community I think it would best fit into our Wiki's structure as 1h – Wish List. Would that be OK?
    • - dalinian 19:20 GMT 06 Jan 11
    • Tim, sounds good to me. How do you make a new section? cx650t on 10 Jan 2011 at 07:00 UTC.
  • My suggestion higher up of a mailing list between co-editors is also in light of this discussion - Francois Brutsch 00:40 UTC 09 Jan 11

Welcome to Lee, our newest Co-Editor

I had a ‘cancel my workspace’ request from Danish Notonadict Ib Kristensen, explaining how he'd become a Co-Editor through a misunderstanding arising from English being his second language. So remembering the comments left by Lee (cx650t at NotionAddicts)...

  • from post #21 onwards on our 'Call Out to join our 'Notion Ink FAQ' Co-Editor Team' thread at NotionAddicts; and
  • on our  2e – Display page

...I thought recruiting Lee to 'fill the vacancy' would be tactical. You can strike up a conversation on the renamed 7e5 – Lee (cx650t) Co-Editor Conversation page.

- dalinian 21:40 GMT 03 Jan 11

 


Organisation of Videos?

Hi Co-Editors, great to see the wiki progressing at such a rapid pace. I was wondering whether we could divide the Video section into categories namely:

1. Official Notion Ink Videos: Videos that were created by the Notion Ink Team

2. Unofficial Notion Ink Videos: Videos that were made by reporters, fans, etc.

This bifurcation would help visitors in selecting videos effectively. -sujith 05:43 GMT 31 Dec 10.

 

Hey, sujith. For now, I kinda like the chronological presentation on 1b – Notion Ink Videos Galore  where 1-4 are Unofficial Notion Ink Videos and 5-6 are Official Notion Ink Videos. But as the number of ADAM videos on t'Internet sky-rockets during and after CES 2011 in early January, we'll likely need to sub-divide into multiple 'Videos Galore' pages, and your schema would be one way to do so, eg '1b1 – Official Notion Ink Videos' and '1b2 – Unofficial Notion Ink Videos'. Anybody have other sub-division schemas to suggest? - dalinian 07:15 31 Dec 10

 

I think that Offical/Unofficial is the most appropriate classification at the basic level. If we are looking at further granularity, then we can, maybe divide the videos into hardware-related, UI related, Apps (maybe? ) and maybe one more for showing video evidence of issues/problems one might face. Just an idea... I am cool with official/unoffical classification also. -Rahul

 


Conversation Pages, One per Co-Editor – Edit Yours Today!

Hi Co-Editors, glad to see improvements happening here. To keep everything open and transparent, I'd like to recommend we create individual Co-Editor Conversation pages, similar to the 'User talk' pages you get at MediaWiki places like Wikipedia. This would help in developing our wiki by focussing and preserving discussions in the most relevant place – so when a particular Co-Editor is taking a specific initiative, such as creating a new section, we can hold relevant conversations about that initiative on the Co-Editor's Conversation page inside the wiki, rather than being obscured and lost in emails, forum posts, etc. Before just making it so, I'd like to take a temperature check from my fellow Co-Editors, to poll your opinions in this idea – please post your comments below, by editing this page. – dalinian 14:30 GMT 25 Dec 10. (Oh, and to those so inclined, Merry Christmas, Happy Holidays, and things of that nature, generally!)   visitors since this edit:

 

Yes, good idea (there isn't any yet, not even for you Dalinian, right?) - Francois Brutsch (must be blind, can't find the signature tool? ['Fraid there isn't one, AFAIK – but manually signing and dating doesn't take long, n'est-ce pas? - dalinian 00:35 30 Dec 10])

 

New Section: 7e – Co-Editor Conversation Pages

I've added 12 Co-Editor Conversation Pages, one for each currently active Co-Editor. Please do feel free to fill yours out with content, and edit the default page header – it'll be one way to get to know each other better. I'll finish doing so on my own Conversation Page sometime tomorrow. - dalinian 00:40 30 Dec 10

 

Example of Content for your Co-Editor Conversation Page

OK, so I've populated my 7e12 – Tim Dalinian Jones (dalinian) Conversation Page with the kind of content I think is just right for me – an you're welcome to be inspired to populate your own Co-Editor Conversation Page with similar or analogous content. - dalinian 10:10 31 Dec 10

 


Evolving structure

Isn't there a danger in including Table of Content numbers (i.e. 7a for this page) in the title of the page? [No, done – dalinian]

 

How do we change the structure (add new pages, change the order)?

I'm asking this because I'd like to create a section 'Dreaming ADAM' to link to Rohan's amazing Prezi presentations between April and December 2009 (e.g.), likely under 1 (by the way, I think 1c should probably be a sub-page for each application, and 1d should go to 3) -Francois Brutsch

 

Hey Francois, grand idea! I have 'Create a fully-illustrated 'HOW TO ADD A NEW PAGE' tutorial' on my 'NI FAQ to do list', and it'll appear on our 7d – Wiki Editing Tips-n-Tricks page. And thanks for supporting the 'Conversation Pages, One per Co-Editor?' idea below: I'll start by adding my own, adding my 'NI FAQ to do list', and include 'Add Conversation Pages, One per Co-Editor' on it (mmmm, recursion <drool> ;-). – dalinian 22:00 GMT 30 Dec 10

 


Limit the number of co-editors?

IMO 15 is more than enough. -Figurelli

 

Do we limit the number of co-editors at this point? Right now, we have over 15 people with editing rights (including administrators). I have temporarily disabled the "Let users request for access" feature.  Should I re-enable it? Should we continue to accept editors? -Rahul

 

 


Comments section

The comments thing at the bottom of the pages would be somewhat alright, but is there a way to make a single page editable by anyone (non-members)? I'm going to look into this. Well... seems like either you can't do it, or you need admin rights or something to make that type of change. -Figurelli

 

On a related note, How does one let the reader to enter comments/suggestions/questions?- Rahul

 

Does the comment section at the bottom of pages work for anyone else? When I click the show all comments button, it doesn't do anything. -Figurelli

 

 


Adam vs. ADAM vs. adam

I was pretty sure that all lowercase was what is being used on the actual units, but I'm also certain that capitalized is how it's normally written when being referred to. Example from Rohan's blog: "That is why Adam is not a tablet".

So what'll it be? I saw someone changing a bunch of "Adam"'s to "ADAM"'s, which is fine if that's what preferred. I personally vote for capitalization only (Adam) as "adam" is too hard to distinguish in a paragraph, but "ADAM" screams too much. Thoughts? - TheGroveJay 03:22 GMT 26 Dec 10

 

I was pondering on raising this issue at some point, so thanks for doing so explicitly now, TheGroveJay. I favour ADAM over Adam or adam. While we know all-caps means shouting in forums, PMs, IM, etc, this is a website, and IMO web users in general (and potential ADAM owners in particular) are sophisticated enough to appreciate the contextual difference. Using ADAM consistently is different from Rohan's usage on the NI blog, but I favour ADAM it because...

  1. ADAM immediately signifies it's the tablet we're talking about, rather than any other entity – eg: Adam the guy in customer services, Adam in the Bible, Adam the tech blogger, etc.
  2. ADAM enables selective dropping of the definite article without ambiguity – eg: "ADAM outputs 1080p video via HDMI" cf. "The Adam outputs 1080p video via HDMI
  3. ADAM makes a real stand-out product really stand-out typographically on a webpage

Your thoughts? - dalinian 09:26 GMT 27 Dec 10

 

Sounds solid to me. I'll have to get used to reading it without shouting it in my mind, not that I don't want to cheer on ADAM! :)  - TheGroveJay 12:47 GMT 27 Dec 10

 

 


New Page: 7d – Wiki Editing Tips-n-Tricks

I’ve made a new page on which we Co-Editors can pass on handy info to make wiki editing easier. Go there now for an illustrated 'How To Make External Links open in a New Window/Tab' tip– dalinian 16:30 GMT 25 Dec 10

New Tip: How To Embed Video - dalinian 09:26 GMT 27 Dec 10

 


Source Citation

I think so as well. I cited a source or two when editing and will keep it up, unless anyone has objections. I'm gonna go through now and straighten up the sections and just remove the roman numerals and letters and just leave bold headers. - Figurelli

 

Wondering if we should have sources cited for everything, might be nice, but take some time to run through everything up here so far. These would presumably link directly to the source

 

I think the superscript hyperlink would be good. Would be better if we used an 'S' or the word 'Source' in brackets in superscript for everything instead of a number like wiki. Doing it like Wikipedia (numbered citations that jump to the bottom of the page) would be a lot more work than it's worth. I think just doing something like: Notion Ink[S] would work fine.

 

Sounds good, and the bracketed 'S' would be much easier in terms of code copying + link changing.

 


New Page 7a – What Is To Be Done

I found the first two items in a conversation on the 7b – Sandbox page, so I made this page to host Co-Editor Team conversations. – dalinian 23:12 GMT 24 Dec 10

 


OTHER DISCUSSIONS

 

Memory Thought...

  • I keep asking and getting different responses concerning the memory for ADAM and just realized something.  There have been various comments about ADAM having 8GB expandable to 128 GB and "every one" keeps asking about which type of MicroSD supports 128 GB?  Maybe because "we" aren't asking the correct way.  I got one answer to a Wordpress Blog comment I made about whether I'm getting 8GB or 10GB in "my" ADAM. I was told that "in fact" it is 10 GB. 2GB comprised of 1GB RAM, 1 GB SLC and 8 GB of eMMC.  That's the clue folks. Toshiba announced last July that they were making 128 GB eMMC chips!. So we "should" be able to increase the on-board memory to 128 GB WITHOUT using any of the USB or the microSD slots.  Yes?
    • It would be nice if Notion Ink would provide answers to at least the "customers". They have my money, why won't they answer my customer questions? (I emailed Notion Ink and haven't received any answer.) – cx650t 05:57 UTC 11 Jan 2011 
  • Hey Lee, while I sympathize with your on-going confusion re ADAM’s memory/storage, I don’t think this is the right place to post about it in these terms, so I’ve moved this to the foot of the list. 7a – What Is To Be Done is “a place where members of the Co-Editor Team can plan, plot, discuss, debate, and so on about improving our NI FAQ Wiki”, while I’d suggest this material would be better posted to the ‘ADAM’s Storage – The microSDXC Mysteries’ thread on the NA forums.

 

 

 


 

« 7 – NI FAQ ADMINISTRATION

NI FAQ Front Page

7 – NI FAQ ADMINISTRATION

7b – Sandbox »

 

Comments (0)

You don't have permission to comment on this page.