Well yes and no that would work. Marking as read only, might be a good thing, to prevent too much 'extra' stuff from being added to the thread.
The main concern, has come down to 'changes'
So say, we put up the guide in a few weeks. List the current firmware revisions, models, etc. All is good.
Then a month from now, rogers releases a new firmware version.. and the menus change, or its called something different, or how you have to do it, is different.
Currently, we can edit a recent post, but anything older, we cant.
We dont want to have to have a 'oh always look at the BOTTOM of the thread for the newest' type of thing 😞
Some way an unlock or something, that we could then go back and edit the ORIGINAL posts to update the content.. (even if its per request.. we want to change it, have to PM you guys to unlock it so we can edit it, etc)
I can give you guys permission as community leaders to edit longer than the current default (24 hours). I have the power!!
You would only have access to edit as the OP. Any other edits would need to be done by one of the mods. Locked just means that others won't be able to comment on it - could be good or bad.
Pros - other users can add tips, context, benefit of their experience
Cons - it confuses the topic because people add more questions but we could just move those to a new thread (as moderators).
Making a thread read-only could work, if a few other steps were also taken.
What if we create and edit/expand the posting on a given subject here in this more restricted area of the Forum. We create a prototype or proposed posting here. At this point we would have the ability to discuss and critique the posting amongst us, and post revised versions of the "document" to the thread, as well as discussions on the topic.
Once we have refined the document/posting to where we believe we have worked out the bugs and issues, and made it as accessible as possible to the wider (probably less technically knowledged) Forum participants at large, we can then repost the item in the area of the Forum where we want this to be posted. At this point the posting becomes read-only.
If in future revisions are required for reasons of changes in firmware, or whatever, we can follow the same process and then either post it in the original thread in the main forum, or create a new thread.
The above process will take some time, and some impassioned/inspired individual will need to step up to the plate to create the original prototyp document on a given subject to trial the whole concept. That individual will need to be capable of receiving hopefully constructive suggestions for improvements or additions.
That leaves one other matter, that of testing the document/process once we have gotten it to the point of near-completion. And finally, someone will need to make the decision that the document is ready for prime time and can be posted in the Forum at large.
OK all, slings and arrows, rotten tomatoes, or whatever you got. Give it to me! Does the above have merit, or should I go back to vacuum tubes.........
I agree, we could do the ROUGH copy here, make sure its formated ok, etc.. before posting it in the regular section.
While i agree it should be proofed and tweeked before posting.. and that done with any MAJOR revisions. Minor revisions could just be done ad hoc, say something like just changing the firmware version #, but the process didnt change, that sort of thing.
With the way the editing would work, etc.. yes, this would have to fall on one person, at least for THAT thread. IE if we do this more often, different people may be in charge of the edits for A and C, but someone else for B document.
While i agree we should review, edit before posting it... i dont want it to be TOOOOO formal, if you get jist.. dont want it to be each change has to go under a review board before being done, etc, etc. 😛 otherwise it becomes too much like a JOB 🙂
Right! We don't want it to be like a job. Rogers would need to pay us, and that would mess up my taxes.
The motivation for my suggestion is that we are proposing to produce postings which hopefully will have some authority for technical quality and factual correctness. Also, the intention as I understand it is that they be a reference for more complicated extensions users may want to make to their home installations. Under normal circumstances these postings would have a longer than normal "lifetime". All of which means to me that we need to ensure a greater than normal degree of thoroughness and quality in our postings.
There are no doubt different ways to approach this. So, let's see what other comments come in.
OK, let's cut to the chase!
1. So far, we haven't yet had any feedback from RogersGina, who I assume we would want/need on board with this concept. Until she responds positively, any action is premature.
2. In order to make this whole "project" more real, we need actual topics/subject matter/areas of interest which we will address. Until we have actual proposed topics, this discussion is hypothetical. Tthe subject of bridging D3 modems and setting up/configuring an external router connection for the various Rogers-supplied modems seems like a possibility. I however, do not use cable, and have no direct experience with this subject. For this topic, would you think a posting for each of the modem/router makes offered by Rogers is required? And what is the impact of different makes/models of external routers which users might wish to connect?
3. Another area which just recently was the subject of some postings is that of DNS benchmarking/optimization. This again will need to be handled differently depending on whether the router has the functionality of changing its DNS settings (my Ericsson W35 does not!). Of course, I could put an external router on my W35, and disable the W35 dhcp functions. DNS performance ought to be of interest to basically all users of the Internet due to its significant effect on normal web browsing activity.
4. Pending approval/concurrance of/with our approach, I am will to take a kick at the DNS subject.
So, who else is there out there with ideas on what needs to be done, and would like to initiate an effort to make it happen?
Don't wait for me! I'm just reading from the sidelines today 🙂
My only suggestion is to post each (draft) topic in a new thread. Also, let me know when you're planning to post live and I can make the post read only.
Just keep in mind that this is a hosted site so there could be times when I'll have to edit a post based on feedback from a product team but I will let you know if that happens!