We are going to be quite busy getting everything ready for the moment of "flipping the switch", but it's still a long way off. We are not going to do that before we're 100% sure that the new site is ready for users and you.
The initial setup will take quite a while, but during that process, we will need your support and assistance with the following areas:
Contributing and reviewing elements of the new site's design
If you have any feedback or questions, please do not send us PMs, IRC messages or emails. Instead, use this thread and the threads listed above. This will make it much easier for everyone to follow and participate in the migration process.
As always, thank you for being there for us and all the users.
Looking forward to an easy migration!
---=====---=====---
Updates
Ist Edit Modified by John99 on August 3, 2016 at 10:20:11 PM +0100 ~J99
Added link to air.mo for community meeting 03 Aug initially mentioned
2nd Edit 15th Aug ~J99
Struck thro the link & mention of the Google Doc [migration document. The Google Doc has in fact never been used by Admins or Contributors since its initial creation.
What are being used, (NOT editable by contributors) as detailed in New Platform Meetings such as the one on 8th Sept are a rather simplistic Trello & a much more informative spreadsheet Lithium Migration Task Breakdown
3rd Edit 29 Sep (Michał)
Moved things around and highlighted the discussion threads for the listed aspects of the migration.
Hi everyone,
As you may know, we are moving SUMO from Kitsune to Lithium. We have presented migration plans [https://public.etherpad-mozilla.org/p/sumo-2016-08-03 during one of the community meetings]. If you missed that meeting, [https://air.mozilla.org/weekly-sumo-community-meeting-august-3-2016/ check the Air Mozilla video]. The material presented during that meeting is [https://docs.google.com/document/d/1PLutbv43xBTnhfleOQwVKUeL6K4V_TSb1xngG0m4pG0/edit# in this document].
We are going to be quite busy getting everything ready for the moment of "flipping the switch", but it's still a long way off. We are not going to do that before we're 100% sure that the new site is ready for users and you.
The initial setup will take quite a while, but during that process, we will need your support and assistance with the following areas:
* Contributing and reviewing elements of the new site's design
** [https://support.mozilla.org/forums/contributors/712184?last=70259 Roles]
** [https://support.mozilla.org/forums/contributors/712183?last=70256 Gamification: ranks & badges]
** [https://support.mozilla.org/forums/contributors/712196?last=70339 Metrics and measurement]
** [https://support.mozilla.org/forums/contributors/712187?last=70340 Design ideas (1st wave)]
** [https://support.mozilla.org/forums/contributors/712195?last=70347 Forum moderation]
** [https://support.mozilla.org/forums/contributors/712208?last=70434 Shutting down Kitsune]
* Testing features and processes on the new platform (this also includes new documentation for new contributors)
** [https://support.mozilla.org/user/Madasan Please contact Madalina if you want to test the new platform].
You can follow the migration process on our [https://trello.com/b/ZZKj4vDw/sumo-lithium-migration-public-board public trello board].
If you have any feedback or questions, please ''do not'' send us PMs, IRC messages or emails. Instead, use this thread and the threads listed above. This will make it much easier for everyone to follow and participate in the migration process.
As always, thank you for being there for us and all the users.
Looking forward to an easy migration!
---=====---=====---
Updates
Ist Edit Modified by John99 on August 3, 2016 at 10:20:11 PM +0100 ~J99
* Added link to air.mo for community meeting [https://air.mozilla.org/weekly-sumo-community-meeting-august-3-2016/ 03 Aug] initially mentioned
2nd Edit 15th Aug ~J99
* Struck thro the link & mention of the Google Doc <s>[[https://docs.google.com/document/d/1PLutbv43xBTnhfleOQwVKUeL6K4V_TSb1xngG0m4pG0/edit# migration document]</s>. The Google Doc has in fact never been used by Admins or Contributors since its initial creation.
* What are being used, ('''NOT editable by contributors''') as detailed in New Platform Meetings such as the one on 8th Sept are a rather simplistic '''[https://trello.com/b/ZZKj4vDw/sumo-lithium-migration-public-board Trello]''' & a much more informative spreadsheet '''[https://docs.google.com/spreadsheets/d/1PFWB36VEJdUik3CLZpiAFvzL4XBpW2I1ve49hrJPvGg/edit#gid=0 Lithium Migration Task Breakdown]'''
3rd Edit 29 Sep (Michał)
* Moved things around and highlighted the discussion threads for the listed aspects of the migration.
The key feature of the existing support forum that I think should be retained is the ability to see (before you open a question) the Firefox version number and the operating system of the user. Allied to this is the ability (once you are "in" a question) to see the full user agent details.
This enables me to instantly see if I know the operating system to be attempt the question and if the user is up to date. For example, I would not open a question relating to OS X, but I might if the question was about Firefox on Linux. I might also see that the user is using an older version of Firefox, but on checking the full user agent details in the question, I may see that they are using a distro version of Firefox and will better understand that in the context of their support questions.
This would save time, but would also give us accurate information with which to help the user. Expecting the user to find and supply this accurately would not work as well as automated capture and display of this information and is something I find very useful.
It is a feature of Kitsune that is easy to overlook, but is something I am sure others find very useful.
Hi
The key feature of the existing support forum that I think should be retained is the ability to see (before you open a question) the Firefox version number and the operating system of the user. Allied to this is the ability (once you are "in" a question) to see the full user agent details.
This enables me to instantly see if I know the operating system to be attempt the question and if the user is up to date. For example, I would not open a question relating to OS X, but I might if the question was about Firefox on Linux. I might also see that the user is using an older version of Firefox, but on checking the full user agent details in the question, I may see that they are using a distro version of Firefox and will better understand that in the context of their support questions.
This would save time, but would also give us accurate information with which to help the user. Expecting the user to find and supply this accurately would not work as well as automated capture and display of this information and is something I find very useful.
It is a feature of Kitsune that is easy to overlook, but is something I am sure others find very useful.
I think it was mentioned in the video we will get an oportunity to test the new forum out pre Release how do we go about that ?
Do contributors see it in the pre acceptance form ?
I note mention of 5 days in which to respond to changes. is all that response going to be in this Thread as far as contributors are concerned.
Do contributors see the response made to Lithium or are you keeping that secret.
I know there was a thread somewhere with a wishlist for the future replacement. Now negotiations will be over & development will be under way what about a list of the features
What will be retained|improved ?
and the features that will be lost ?
Some examples
Must Login: I trust users will need to log in before posting questions.
System Details: Besides the User Agent String is the new forum going to try to extract or prompt for extension details, Information Page details etc
Included Products: Will this be Firefox only or the existing list or e something in between.
MobileOptimised Version: Does it have a mobile optimised version (I guess that is standared and essential these days)
Tagging & Categories IMO those could have been improved in Kitsune, Will it still have Tagging, categories, Topics ? What is the spec?
Search & Advanced Search: What do we get, what is the spec ?
Quotes & Blockquotes: Will it allow block quotes & post quoting. I imagine it will that must be standard on most fora.
Legacy Posts LINKING: Will the new forum scramble and break most of the carefully crafted links in existing posts ?
Showfor: Do I recall someone mentioning that was one of the things we would agreed was very important to retain.
Moderation: Tools and features ? : including spam alerts/ filtering blocking
I think it was mentioned in the video we will get an oportunity to test the new forum out pre Release how do we go about that ?
Do contributors see it in the pre acceptance form ?
I note mention of 5 days in which to respond to changes. is all that response going to be in this Thread as far as contributors are concerned.
Do contributors see the response made to Lithium or are you keeping that secret.
I know there was a thread somewhere with a wishlist for the future replacement. Now negotiations will be over & development will be under way what about a''' list of the features'''
* What will be retained|improved ?
* and the features that will be lost ?
Some examples
# Must Login: <br/>I trust users will need to log in before posting questions.
#System Details: <br/> Besides the User Agent String is the new forum going to try to extract or prompt for extension details, Information Page details etc
# Included Products: <br/>Will this be Firefox only or the existing list or e something in between.
# MobileOptimised Version: <br/>Does it have a mobile optimised version (I guess that is standared and essential these days)
#Tagging & Categories <br/>IMO those could have been improved in Kitsune, Will it still have Tagging, categories, Topics ? What is the spec?
# Search & Advanced Search: <br> What do we get, what is the spec ?
# Quotes & Blockquotes: <br/>Will it allow block quotes & post quoting. I imagine it will that must be standard on most fora.
# Legacy Posts LINKING: <br/> Will the new forum scramble and break most of the carefully crafted links in existing posts ?
# Showfor: <br/>Do I recall someone mentioning that was one of the things we would agreed was very important to retain.
# Moderation: Tools and features ? :<br> including spam alerts/ filtering blocking
At this stage we're waiting for the Lithium folks to put together a team on their end and then we will kick things off.
There will be absolutely no secrets. I expect the contributor community to be fully immersed in the transition process. I'm not sure exactly how communication will look like with the Lithium folks (as in are we going to have them attend our meetings or organize something else, are we going to get them introduced on this thread etc) but that's one of the first things we will discuss once they are ready to go. They are a SAAS company used to deal with corporate clients mostly so there will be some "training" required for them to understand how we work, but I'm very positive about it. On the SUMO side we will continue using the forums here and the Platform meetings on Thursday for 100% transparency on the process. There will be testing environments available for everyone. There might be some NDA requirements for accessing some of the testing tools but almost everybody here is under NDA so it shouldn't be a problem.
The only thing that we need to keep in mind as a community is that we will have hard deadlines for designing specific processes or for giving the feedback required for the transition. We will need to make sure everybody who has something to say does so in due time.
On the features side we are trying to keep as many as the original features as possible but, obivously, not everything will be the same. Some features might be missing, some features might be there but look different and some features will have to be added later, one at a time, depending on the priority.
So far I can say that things like forum moderation, tagging, search, mobile optimization, logins will be there out of the box. Features like ShowFor or user agent do not come out of the box with Lithium but can be added. I expect we will want to have at least the ShowFor part ready before we go live.
In the next couple of months we will do a lot of work around designing how certain features, processes or pages will work on Lithium so I hope people will be able to participate. This is an opportunity for us to actually make some things better.
Thanks for commenting Seburo, John99
At this stage we're waiting for the Lithium folks to put together a team on their end and then we will kick things off.
There will be absolutely no secrets. I expect the contributor community to be fully immersed in the transition process. I'm not sure exactly how communication will look like with the Lithium folks (as in are we going to have them attend our meetings or organize something else, are we going to get them introduced on this thread etc) but that's one of the first things we will discuss once they are ready to go. They are a SAAS company used to deal with corporate clients mostly so there will be some "training" required for them to understand how we work, but I'm very positive about it. On the SUMO side we will continue using the forums here and the Platform meetings on Thursday for 100% transparency on the process. There will be testing environments available for everyone. There might be some NDA requirements for accessing some of the testing tools but almost everybody here is under NDA so it shouldn't be a problem.
The only thing that we need to keep in mind as a community is that we will have hard deadlines for designing specific processes or for giving the feedback required for the transition. We will need to make sure everybody who has something to say does so in due time.
On the features side we are trying to keep as many as the original features as possible but, obivously, not everything will be the same. Some features might be missing, some features might be there but look different and some features will have to be added later, one at a time, depending on the priority.
So far I can say that things like forum moderation, tagging, search, mobile optimization, logins will be there out of the box. Features like ShowFor or user agent do not come out of the box with Lithium but can be added. I expect we will want to have at least the ShowFor part ready before we go live.
In the next couple of months we will do a lot of work around designing how certain features, processes or pages will work on Lithium so I hope people will be able to participate. This is an opportunity for us to actually make some things better.
My ISP recently switched to Lithium for their forum, and I find it clunkier than the old one. Yes it's OK and usable, but a step backwards IMHO - a bit like Australis... oops now I'm in trouble!
My ISP recently switched to Lithium for their forum, and I find it clunkier than the old one. Yes it's OK and usable, but a step backwards IMHO - a bit like Australis... oops now I'm in trouble!
https://community.plus.net/t5/Community-Site-Feedback/bd-p/Community
The main reason for moving to another platform is that unfortunately we do not have the resources to keep developing a platform of our own. We have had no developers working on Kitsune in more than half a year and bugs are piling up :/
Obviously it's hard for a 3rd party platform to feel as smooth as one that you are developing for your own unique needs but it is not impossible. It's really up to us on how we set up the migration so that we get the best experience possible out of the new platform.
Haha, you're not in trouble :)
The main reason for moving to another platform is that unfortunately we do not have the resources to keep developing a platform of our own. We have had no developers working on Kitsune in more than half a year and bugs are piling up :/
Obviously it's hard for a 3rd party platform to feel as smooth as one that you are developing for your own unique needs but it is not impossible. It's really up to us on how we set up the migration so that we get the best experience possible out of the new platform.
Sorry if this was already covered in one of the meetings but,
What about common forum responses? Will these responses still be available and accessible to contributors as part of a canned response tool for replies in the new support forum?
What about old support threads? Will they still be available via search engines or through an internal search? It would be a shame to lose all of that content. Both users and contributors make use of support threads going back months or sometimes years in the past, to answer current questions.
Sorry if this was already covered in one of the meetings but,<br>
What about [[common forum responses]]? Will these responses still be available and accessible to contributors as part of a canned response tool for replies in the new support forum?
What about old support threads? Will they still be available via search engines or through an internal search? It would be a shame to lose all of that content. Both users and contributors make use of support threads going back months or sometimes years in the past, to answer current questions.
There is now a mass of information relating to many documents, and presumably very many changes or proposals in the thread
* ''We are having an audit…..don’t worry its for the new platform'' [/forums/contributors/712112]
Sorry if this was already covered in one of the meetings but,
What about common forum responses? Will these responses still be available and accessible to contributors as part of a canned response tool for replies in the new support forum?
What about old support threads? Will they still be available via search engines or through an internal search?
Yes we are going to have some form of canned responses. It might look different and I'm not sure whether it will be available right away in terms of priority but it is definitely on the list.
As per old support threads, I'm not sure how much we can migrate but we will definitely try to find a solution to have that content available one way or another.
Again, many of the responses will come as we work through the migration as now it is hard to tell what we can do right away and what we cannot.
''AliceWyman [[#post-69843|said]]''
<blockquote>
Sorry if this was already covered in one of the meetings but,<br>
What about [[common forum responses]]? Will these responses still be available and accessible to contributors as part of a canned response tool for replies in the new support forum?
What about old support threads? Will they still be available via search engines or through an internal search?
</blockquote>
Yes we are going to have some form of canned responses. It might look different and I'm not sure whether it will be available right away in terms of priority but it is definitely on the list.
As per old support threads, I'm not sure how much we can migrate but we will definitely try to find a solution to have that content available one way or another.
Again, many of the responses will come as we work through the migration as now it is hard to tell what we can do right away and what we cannot.
So long, Kitsune ... :'-( † † † † † Sometimes I wonder if Google or someone is bribing Mozilla to degrade everything good we have.
I have avoided this discussion till now and hoped that this migration is a stupid idea that will sink into oblivion among many others. But I could have already learnt that if big guys decide something, there's no chance of making it different. I daresay nobody of us is really happy with this - almost everyone voted to stay on Kitsune. "Product team wants to focus on developing Firefox..."? Judging by the number of idiotic features and revamps shipped into Firefox recently, Firefox has already had too many developers.
But let's calm down now, 'cause I don't want to get on the wrong side of the moderators. I'll rather ask some questions that concern me the most:
Will the SUMO visual theme stay same (or similar)? If we start using some default standard design that would be a first choice for the local gardening community site, it'll be a huge step backwards and Mozilla will give an impression of a community that isn't able to maintain a decent help site, let alone develop a decent browser. Mozilla has already lost a lot of trust recently and it can't afford to lose more.
How much will the sitemap change? Will users need ages to find the new correct place to ask a question, and I'll spend a whole day to learn how to use the new platform? Are old links going to break? I hope not...
Looking at Lithium's website, it seems to mainly focus on forums and social channels. How about KB and L10N? Do they have a good platform for this? Are they going to listen to us and maintain everything we need in a decent time after we start using their platform?
... Sorry if those questions have already been answered ... I've just started following the topic.
So long, Kitsune ... :'-( † † † † † Sometimes I wonder if Google or someone is bribing Mozilla to degrade everything good we have.
I have avoided this discussion till now and hoped that this migration is a stupid idea that will sink into oblivion among many others. But I could have already learnt that if big guys decide something, there's no chance of making it different. I daresay nobody of us is really happy with this - [https://docs.google.com/document/d/1mYIx-6ZzRmb-cug5s8wgEQG5meNBqikpAtq-D768j5Y/edit#heading=h.ho1hdzp3mjzq almost everyone voted to stay on Kitsune]. "Product team wants to focus on developing Firefox..."? Judging by the number of idiotic features and revamps shipped into Firefox recently, Firefox has already had too many developers.
But let's calm down now, 'cause I don't want to get on the wrong side of the moderators. I'll rather ask some questions that concern me the most:
* '''Will the SUMO visual theme stay same (or similar)?''' If we start using some default standard design that would be a first choice for the local gardening community site, it'll be a huge step backwards and Mozilla will give an impression of a community that isn't able to maintain a decent help site, let alone develop a decent browser. Mozilla has already lost a lot of trust recently and it can't afford to lose more.
* '''How much will the sitemap change?''' Will users need ages to find the new correct place to ask a question, and I'll spend a whole day to learn how to use the new platform? Are old links going to break? I hope not...
* Looking at [http://www.lithium.com/products-solutions/ Lithium's website], it seems to mainly focus on forums and social channels. '''How about KB and L10N? Do they have a good platform for this? Are they going to listen to us and maintain everything we need in a decent time ''after'' we start using their platform?
... Sorry if those questions have already been answered ... I've just started following the topic.
Theme & Logos
Sounds like a redesign or refresh is in progress ca 5min:50sec
KB
Sounds like a total change will occur.
It appears Joni expects to have new compressed articles ready shortly re Sumo. (That's towards the end ca 10min:10sec)
That makes me wonder what will happen to individual Live KB articles. Is community editing and production of KB articles even going to exist on Lithium ?
?? Will most KB documents be moved and based elsewhere ?? for instance would we have to fall back on wiki.mozilla.org
This is from seeing the ca 16 minute airmo https://air.mozilla.org/sumo-platform-meeting-august-18-2016/
The agenda for that was mentioned ca 0min:40sec but I did not locate that.
Theme & Logos
Sounds like a redesign or refresh is in progress ca 5min:50sec
KB
Sounds like a total change will occur.
It appears Joni expects to have new compressed articles ready shortly re Sumo. (That's towards the end ca 10min:10sec)
That makes me wonder what will happen to individual Live KB articles. Is community editing and production of KB articles even going to exist on Lithium ?
?? Will most KB documents be moved and based elsewhere ?? for instance would we have to fall back on wiki.mozilla.org
Theme & Logos
Sounds like a redesign or refresh is in progress ca 5min:50sec
"Sumo needs a little bit of visual refresh ... I don't think it needs to be something super drastic..." will it be us who will (re)design it? Or are we going to stick with some ready-made Lithium design?
KB
Sounds like a total change will occur.
It appears Joni expects to have new compressed articles ready shortly re Sumo. (That's towards the end ca 10min:10sec)
That makes me wonder what will happen to individual Live KB articles. Is community editing and production of KB articles even going to exist on Lithium ?
Years of hard voluntary work by KB editors and localizers going "u pičku materinu"? That simply can't be. Did I, did we sacrifice so much of our free time to have our work deleted now? Nobody of us is going to stand still and watch this happen.
''John99 [[#post-69979|je rekel]]''
<blockquote>
Theme & Logos
Sounds like a redesign or refresh is in progress ca 5min:50sec
</blockquote>
''"Sumo needs a little bit of visual refresh ... I don't think it needs to be something super drastic..."'' will it be us who will (re)design it? Or are we going to stick with some ready-made Lithium design?
''John99 [[#post-69979|je rekel]]''
<blockquote>
KB
Sounds like a total change will occur.
It appears Joni expects to have new compressed articles ready shortly re Sumo. (That's towards the end ca 10min:10sec)
That makes me wonder what will happen to individual Live KB articles. Is community editing and production of KB articles even going to exist on Lithium ?
</blockquote>
Years of hard voluntary work by KB editors and localizers going "u pičku materinu"? That simply can't be. Did I, did '''we''' sacrifice so much of our free time to have our work deleted now? Nobody of us is going to stand still and watch this happen.
I don't think there is any way we are going to lose everything, KB wise; and we are sure to have the original articles available at least for some time.
But I have no idea what the future holds other than what is in these threads and the Platform Video meeting.
I am sure the basics of some of this will have been decided by Admins before settling on migrating to Lithium. Obviously Admins are taking action already on rewriting some KB articles &/or webpages - but it still is unclear to me what is in progress and the requirements for such a rewrite. This is a weekend so hopefully more info will be forthcoming on Monday. Obviously things will have to move quickly, but I hope we are kept in the loop, rather than being informed after decisions have been made and are being implemented..
No idea about L10n but again I am sure decisions will have been made, and I am equally sure L10n will continue. It is unthinkable that we would lose L10n of KB articles. However I am again surprised we do not know more about what is happening and have some outline of what is likely.
I don't think there is any way we are going to lose everything, KB wise; and we are sure to have the original articles available at least for some time.
But I have no idea what the future holds other than what is in these threads and the Platform Video meeting.
I am sure the basics of some of this will have been decided by Admins before settling on migrating to Lithium. Obviously Admins are taking action already on rewriting some KB articles &/or webpages - but it still is unclear to me what is in progress and the requirements for such a rewrite. This is a weekend so hopefully more info will be forthcoming on Monday. Obviously things will have to move quickly, but I hope we are kept in the loop, rather than being informed after decisions have been made and are being implemented..
No idea about L10n but again I am sure decisions will have been made, and I am equally sure L10n will continue. It is unthinkable that we would lose L10n of KB articles. However I am again surprised we do not know more about what is happening and have some outline of what is likely.
I don't think there is any way we are going to lose everything, KB wise; and we are sure to have the original articles available at least for some time.<snip> Obviously Admins are taking action already on rewriting some KB articles &/or webpages - but it still is unclear to me what is in progress and the requirements for such a rewrite.
As I understand it, Joni is working on rewriting and consolidating "How to contribute" articles for KB editors, not support articles. See this KB Google doc that Rachel posted in the "We are having an audit" thread.
As far as KB support articles, I'm under the impression that all of the Live "How to" and "Troubleshooting" articles will be migrated. Templates also should be migrated since they're part of support articles. However, due to an old bug, Templates aren't listed in the KB Dashboard overview.
''John99 [[#post-69986|said]]''
<blockquote>
I don't think there is any way we are going to lose everything, KB wise; and we are sure to have the original articles available at least for some time.<snip> Obviously Admins are taking action already on rewriting some KB articles &/or webpages - but it still is unclear to me what is in progress and the requirements for such a rewrite.
</blockquote>
As I understand it, Joni is working on rewriting and consolidating "How to contribute" articles for KB editors, not support articles. See this [https://docs.google.com/spreadsheets/d/1qiS-RpnVMPx8-6bpEUjKJeR0xABRPRVBQHs-gwm6fDA/edit?usp=sharing KB Google doc] that Rachel posted in the "[https://support.mozilla.org/en-US/forums/contributors/712112 We are having an audit]" thread.
As far as KB support articles, I'm under the impression that all of the Live "How to" and "Troubleshooting" articles will be migrated. [https://support.mozilla.org/en-US/kb/category/60 Templates] also should be migrated since they're part of support articles. However, due to an old bug, Templates aren't listed in the [https://support.mozilla.org/en-US/contributors/kb-overview?product= KB Dashboard overview].
... See this KB Google doc that Rachel posted in ....
That link gives a You need permission page for me.
I may need to check which account I use - Google & Sumo use different email addresses, or maybe I was not given permission to access that. I will have to go through the links in Rachel's thread again.
As far as KB support articles, I'm under the impression that all of the Live "How to" and "Troubleshooting" articles will be migrated. Templates also should be migrated since they're part of support articles. However, due to an old bug, Templates aren't listed in the KB Dashboard overview.
Interesting. So from somewhere you discovered the migration appears to be based on what is listed in the en-US KB dashboard.
You mention live articles, any impression as to what happens if the articles status happens to be needs review? I trust that will not block the migration of the current parent document.
Any insight in to the L10n position?
Will L10n articles linked from the KB dashboard all be migrated?
(Vesper mentioned the KB/L10n Gallery elsethread /forums/l10n-forum/712113?last=69974#post-69893 )
Does anyone know the position with L10n or locale versions of the Lithium forum itself ?
Both for the UI and more importantly for the active communities for instance we have a very active pt-BR community and other less active specific locales posting in their own languages.
The idea of keeping all info in or linked from this thread and the one Google Doc to enable us to find information easily and quickly may not be holding together as well as it could have. It does still seem a good idea as long as people add the links and information in a timely manner, especially to the top level post and document.
Thanks Alice
''AliceWyman [[#post-69987|said]]''
<blockquote> ... See this [https://docs.google.com/spreadsheets/d/1qiS-RpnVMPx8-6bpEUjKJeR0xABRPRVBQHs-gwm6fDA/edit?usp=sharing KB Google doc] that Rachel posted in .... </blockquote>
That link gives a ''You need permission'' page for me.
I may need to check which account I use - Google & Sumo use different email addresses, or maybe I was not given permission to access that. I will have to go through the links in Rachel's thread again.
<blockquote>
As far as KB support articles, I'm under the impression that all of the Live "How to" and "Troubleshooting" articles will be migrated. [https://support.mozilla.org/en-US/kb/category/60 Templates] also should be migrated since they're part of support articles. However, due to an old bug, Templates aren't listed in the [https://support.mozilla.org/en-US/contributors/kb-overview?product= KB Dashboard overview].
</blockquote>
Interesting. So from somewhere you discovered the migration appears to be based on what is listed in the en-US KB dashboard.
You mention live articles, any impression as to what happens if the articles status happens to be needs review? I trust that will not block the migration of the current parent document.
Any insight in to the L10n position?
Will L10n articles linked from the KB dashboard all be migrated?
(Vesper mentioned the KB/L10n Gallery elsethread [/forums/l10n-forum/712113?last=69974#post-69893] )
Does anyone know the position with L10n or locale versions of the Lithium forum itself ?
Both for the UI and more importantly for the active communities for instance we have a very active pt-BR community and other less active specific locales '''posting in their own languages'''.
The idea of keeping all info in or linked from this thread and the one Google Doc to enable us to find information easily and quickly may not be holding together as well as it could have. It does still seem a good idea as long as people add the links and information in a timely manner, especially to the top level post and document.
Update
I have now checked the links in Rachel's thread for Google Docs. Only the KB one is not letting me see it. I have put in a permission request, although I thought I had already done that.
Also I have no idea where the new agenda Google Doc is - apparently that is open, presumably for the last and the next platform meeting.
The L10n document is only about the guidelines and I am not sure it is being discussed and edited yet. That's the impression I got from the platform video of the 18th unless of course it is part of the get involved page.
I also note Madalina mentioned twice that training documentation is available now for the new platform ca 7m:15s & ca12m:30s
Update
I have now checked the links in Rachel's thread for Google Docs. Only the KB one is not letting me see it. I have put in a permission request, although I thought I had already done that.
Also I have no idea where the new agenda Google Doc is - apparently that is open, presumably for the last and the next platform meeting.
The L10n document is only about the guidelines and I am not sure it is being discussed and edited yet. That's the impression I got from the platform video of the 18th unless of course it is part of the get involved page.
I also note Madalina mentioned twice that training documentation is available now for the new platform ca 7m:15s & ca12m:30s
... See this KB Google doc that Rachel posted in ....
That link gives a You need permission page for me.
(Using my gmail address, which is also the address listed in my mozillians account) I didn't need permission to access and view the google doc, which is titled KB training audit. I did have to ask for an invitation to edit the document, which Joni gave me.
Interesting. So from somewhere you discovered the migration appears to be based on what is listed in the en-US KB dashboard.
You mention live articles, any impression as to what happens if the articles status happens to be needs review? I trust that will not block the migration of the current parent document.
I don't know how the articles will be migrated to use the Lithium software. by "Live" articles I meant those that were already approved for the KB, including current articles with pending revisions. I don't know what will happen to archived articles, proposed articles never approved for the KB or articles in the "Administration" category (like the new Your hardware is no longer supported article) that have not been moved to the "How to" or "Troubleshooting" support categories. I mentioned that templates were not included in the KB Dashboard Overview just in case that Dashboard was part of the process. The KB google doc does list Using templates with the comment, Might need to rewrite UI bits for Lithium.
Any insight in to the L10n position?
No. Hopefully an admin will answer any L10n migration questions.
''John99 [[#post-69989|said]]''
<blockquote>
''AliceWyman [[#post-69987|said]]''
<blockquote> ... See this [https://docs.google.com/spreadsheets/d/1qiS-RpnVMPx8-6bpEUjKJeR0xABRPRVBQHs-gwm6fDA/edit?usp=sharing KB Google doc] that Rachel posted in .... </blockquote>
That link gives a ''You need permission'' page for me. </blockquote>
(Using my gmail address, which is also the address listed in my mozillians account) I didn't need permission to access and view the google doc, which is titled ''KB training audit''. I did have to ask for an invitation to edit the document, which Joni gave me.
<blockquote>
Interesting. So from somewhere you discovered the migration appears to be based on what is listed in the en-US KB dashboard.
You mention live articles, any impression as to what happens if the articles status happens to be needs review? I trust that will not block the migration of the current parent document.</blockquote>
I don't know how the articles will be migrated to use the Lithium software. by "Live" articles I meant those that were already approved for the KB, including current articles with pending revisions. I don't know what will happen to archived articles, proposed articles never approved for the KB or articles in the "Administration" category (like the new [[Your hardware is no longer supported]] article) that have not been moved to the "How to" or "Troubleshooting" support categories. I mentioned that templates were not included in the [https://support.mozilla.org/en-US/contributors/kb-overview?product= KB Dashboard Overview] just in case that Dashboard was part of the process. The KB google doc does list [[Using templates]] with the comment, ''Might need to rewrite UI bits for Lithium''.
<blockquote>
Any insight in to the L10n position?
</blockquote>
No. Hopefully an admin will answer any L10n migration questions.
This is going slightly off topic, but others could have similar issues if we are using google docs now instead of etherpads etc.
I follow bugzilla on a specific email address. I have another email address shown on mozillians and used for sumo but that is not a gmail address. As it stands I have no access at all to the KB Google doc I can not even view it
The other Google docs I can view and edit with my gmail address.
This is going slightly off topic, but others could have similar issues if we are using google docs now instead of etherpads etc.
I follow bugzilla on a specific email address. I have another email address shown on mozillians and used for sumo but that is not a gmail address. As it stands I have no access at all to the KB Google doc I can not even view it
The other Google docs I can view and edit with my gmail address.
John99,
If you asked for permission and still can't view the KB google doc I would mention that in the We are having an audit thread and /or send an email to Joni and tell her about the problem.
John99,
If you asked for permission and still can't view the [https://docs.google.com/spreadsheets/d/1qiS-RpnVMPx8-6bpEUjKJeR0xABRPRVBQHs-gwm6fDA/edit?usp=sharing KB google doc] I would mention that in the [/forums/contributors/712112 We are having an audit thread] and /or send an email to [/user/jsavage Joni] and tell her about the problem.
What about the [/forums Contributor forums] and [https://support.mozilla.org/en-US/kb/all/discussions Article discussions]? The [/forums/contributors/ SUMO community discussions forum] threads go back to Dec 2007. The [https://support.mozilla.org/en-US/forums/knowledge-base-articles KB articles forum] threads go back to Jan 2009 and the individual KB article discussions go back to Dec 2010. Will those threads be saved or lost?
