Here are the latest commented ideas about launchpad.net .
Reminder for Launchpad
Written by Gustavo Silva the 13 Jun 13 at 21:56.
New
Hey there.
It's not the first time I decided to translate something and, whenever I close my browser, I forget where I saw that page/package/something else needing a translation. I know I can change some settings to open the browser where I closed it, but seems unnecessary to have 6 or 7 pages opened related to Ubuntu.
Cheers
Solution #1:
Give the ability to edit/delete a comment in a bug report
I propose to divide between administrator and user:
administrator:
- should be able to edit or delete every comment
user:
- should be able to edit or delete his own comment, if it's the last in a bug report
Besides a preview of comments would be great.
I propose to divide between administrator and user:
administrator:
- should be able to edit or delete every comment
user:
- should be able to edit or delete his own comment, if it's the last in a bug report
Besides a preview of comments would be great.
Solution #2:
new launchpad feature
When you get a crash report, I think the user should just have to click send report to developers and be done with it. It takes to long to post a bug, which makes some users not want to post bugs. I suggest that the launchpad have a new feature that automatically finds the best match to a bug without the user even having to open the web browser. This would give the developers a wider spectrum of bugs, and would eliminate redundant posts.
When you get a crash report, I think the user should just have to click send report to developers and be done with it. It takes to long to post a bug, which makes some users not want to post bugs. I suggest that the launchpad have a new feature that automatically finds the best match to a bug without the user even having to open the web browser. This would give the developers a wider spectrum of bugs, and would eliminate redundant posts.
Solution #3:
awesome comments system
Launchpad comments system, needs to be awesome.
-Integration of Launchpad Karma in comments.
-Highlight comments from developers and good karma users.
-Implement hierarchy of comments. So talks don't be spreaded.
Launchpad comments system, needs to be awesome.
-Integration of Launchpad Karma in comments.
-Highlight comments from developers and good karma users.
-Implement hierarchy of comments. So talks don't be spreaded.
Launchpad: Data field for users to inform their UbuntuForums, AskUbuntu handles
Written by Effenberg0x0 the 6 May 12 at 17:27.
New
(The same was posted to Launchpad at
https://bugs.launchpad.net/bugs/995309, but triagers requested it to be moved here)
It's hard for a team manager to keep track of its members now that we have many Ubuntu-related online platforms: Launchpad, UbuntuForums, AskUbuntu, irc.ubuntu.com. It's frequent to see users that have different logins / user names for each of these platforms. Launchpad already has a text field in which users can fill in their IRC nicknames. It would make things a lot easier if we also had fields for them to input their UbuntuForums, AskUbuntu handles.
Regards,
Effenberg
Replace anti-spam submission interval
Written by stoffel the 21 Dec 09 at 21:45.
New
When thinking up new ideas or solutions, at some moments you get a load of good ideas or solutions in your brain. Being very productive at such moments, you want to post them all at once so that they don't get lost and so that you possibly find other ideas while your brain is still very active.
Currently, you see this error in such occasions: "To prevent spam, there is a 5 minutes minimum interval between each solution submission. Please wait."
Whilst it is a good thing to prevent spam, it is not a good thing to interrupt creative eureka moments in the brain of contributors.
create a glossary for translations in launchpad
Written by rinia_iku the 18 Nov 09 at 14:07.
New
Sometimes I find very difficult to translate a word properly as the same word is translated differently in different projects or even in the same project by different translators.
as an example the word "File" in Albanian, sometimes I find it "Skedar" sometimes "Document" sometimes even "File" without any real translation and more which I don't remember for the moment.
I think this leads to confusion of users and makes it hard for translators.
Ubuntu free webmail
Written by nitrofurano the 30 Sep 08 at 11:06.
New
As everybody used to know, @mac.com and @hotmail.com are usually popular webmail accounts strongly related with some operating systems, which used to help on their popularity, specially from their users.
The most close of this we can get is opening a linuxmail.org webmail account, but i think would be interesting Canonical providing free webmail account, where we can, for example, use there our launchpad.net login+pwd, like we used with shipit.
Use upstream translations
Written by hendi the 28 Feb 08 at 18:24.
New
Please make it possible to - at least optionally - use the translations provided by upstream, e.g. GNOME and KDE. Their translators do a very good job at producing high-quality, consistent translations. It's a shame that these got replaced by lesser quality suggestions from Rosetta in the past, or are still stuck in Rosetta for several months.
I respect if you insist on using your Launchpad and Rosetta platform for translations, but please at least offer a way to use the translations from upstream. What about "language-pack-XX-upstream"?
Link in repository for the current release
Written by Ivan1986 the 21 Aug 10 at 21:36.
New
I switched from Debian to Ubuntu and a little surprised that instead of simply solving the current release uses a complex system with corrections source.list files.
Translators sometimes don't understand translated strings
Written by Yaron the 5 Oct 10 at 09:36.
New
Sometimes its hard to figure what does a certain string means, sometimes the translator will have to install the app in order to understand what's the purpose of the strings but there are cases where not all strings are visible (different versions) and there are even some apps that the translator cannot install due to various reasons.
Solution #1:
Add screenshot of the apps in Launchpad
Written by
Yaron the 5 Oct 10 at 09:36.
Add a function to Launchpad to add screenshots of the various apps and having the ability to link between a certain area of the image to a string so when trying to translate a string the translator will be able to actually look at the place where this string appears making it easier for him to understand its purpose.
Also vice versa, having the ability to locate strings via images of the app, this step requires some thinking since menus should be linked to dialogs and string for translation.
This issue has been discussed in the Ubuntu mailing list.
Add a function to Launchpad to add screenshots of the various apps and having the ability to link between a certain area of the image to a string so when trying to translate a string the translator will be able to actually look at the place where this string appears making it easier for him to understand its purpose.
Also vice versa, having the ability to locate strings via images of the app, this step requires some thinking since menus should be linked to dialogs and string for translation.
This issue has been discussed in the Ubuntu mailing list.
Solution #2:
Add a link to see the source code where the string is being used
Written by
snabb the 14 Oct 10 at 11:33.
The interface already displays the file and the line number of the source code where the string is being used, but there is no way to easily to jump to a display of the relevant source code.
There should be a link which takes the translator to a screen which shows the pieces of code where the string is being used. Inspecting the code is the only way to be sure how the string is being used and what is the logic related to the particular string. Understanding the program logic is the only way to make good translations in many cases.
Some strings appear only in rare circumstances, so having the program installed and playing around with it while translating does not necessarily help.
The previous idea about having screenshots is technically unfeasible to implement without a lot of manual work. Some strings appear only in extreme circumstances. Also screenshot does not necessarily help the translator understand the program logic the way reading the source code does.
The interface already displays the file and the line number of the source code where the string is being used, but there is no way to easily to jump to a display of the relevant source code.
There should be a link which takes the translator to a screen which shows the pieces of code where the string is being used. Inspecting the code is the only way to be sure how the string is being used and what is the logic related to the particular string. Understanding the program logic is the only way to make good translations in many cases.
Some strings appear only in rare circumstances, so having the program installed and playing around with it while translating does not necessarily help.
The previous idea about having screenshots is technically unfeasible to implement without a lot of manual work. Some strings appear only in extreme circumstances. Also screenshot does not necessarily help the translator understand the program logic the way reading the source code does.
Solution #3:
Allow reporting in an easier way
Written by
Yaron the 27 Jan 11 at 08:19.
Motivation:
In Ubuntu the "Translate this Application" menu item under Help has become completely useless recently and I think we should consider an alternative while utilising gnome-screenshot and apport.
Our goal is to enable an easy and quick way to report typos in apps, in the attached picture I described 5 simple steps to do so (this can also help detect visual glitches in apps or RTL problem, just a thought).
Possible cons:
The app in undetectable or the user decides to report a typo in a website while thinking this is a problem with the app (although highly plausible).
There will be too many bug reports to handle, Launchpad changes are required for this to work.
1st step:
After spotting the typo the users can just click on Help -> Report a broken translation.
This action will launch a series of actions starting with gnome-screenshot -a (that will capture a specific area of the screen) the next actions should somehow prepare the file and add save it to a temp folder (/tmp in our case, gnome-screenshot).
2nd step:
The user will be presented with a crosshair so he can select the desired area, (small floating message on top to bottom of the screen is optional, we have to make sure that the screenshot tool will not capture the message ☺)
3rd step:
The user will have an option to state exactly what seems wrong in his opinion and offer a correction. (in 2 distinct text boxes, 3rd box for comments is optional and I didn't add that in the mockup)
Another option we can offer (does not appear in the mockup) is to add a small window on top that will show the user a thumbnail of the captured area.
4th step:
The following screen associates the typo report to the user using 3 options:
The user will have the ability to log into his Launchpad account.
The user does not have a Launchpad account and he decides this is the right time to sign up.
The user have no interest in a Launchpad account, but he wishes to be informed of any further progress.
The first option will show a username/password boxes for logging in.
The second option will open the default browser with a registration pag, the two option are: sending the report at this step and not publishing it until the user sign up, if the user does not sign up the report is deleted within 24 hrs, the second option is adding a message at the end of the registration progress, at this point the user will dismiss the browser window and go back to the report window where he can sign in and continue.
The third option will show a text box for entering an email address and a captcha (turing test) and a checkbox so the user will have the option to subscribe, we should consider whether its safe to let the users submit reports anonymously.
This step involves the usage of apport (which I'm not familiar with), apport will collect the needed info about the system language etc. including the app name and version and will make sure that the report is good enough, apport also has the option of adding files to Lunchpad bug reports, this makes reporting a little more automatic (future thoughts: make this a GNOME native function using bug-buddy).
5th step:
The final screen, which shows a short greeting (your bug report has been submitted or otherwise not submitted in case there was an error and maybe even tells you what went wrong).
The link to the bug in the middle.
And finally a short message that thanks the user for taking the time to make the open source better.
<img height=20% width=20% src="http://ubuntuforums.org/attachment.php?attachmentid=182866&d=1297008588"><img height=20% width=20% src="http://ubuntuforums.org/attachment.php?attachmentid=182867&d=1297008588"><img height=20% width=20% src="http://ubuntuforums.org/attachment.php?attachmentid=182868&d=1297008588"><img height=20% width=20% src="http://ubuntuforums.org/attachment.php?attachmentid=182869&d=1297008588"><img height=20% width=20% src="http://ubuntuforums.org/attachment.php?attachmentid=182870&d=1297008588">
Motivation:
In Ubuntu the "Translate this Application" menu item under Help has become completely useless recently and I think we should consider an alternative while utilising gnome-screenshot and apport.
Our goal is to enable an easy and quick way to report typos in apps, in the attached picture I described 5 simple steps to do so (this can also help detect visual glitches in apps or RTL problem, just a thought).
Possible cons:
The app in undetectable or the user decides to report a typo in a website while thinking this is a problem with the app (although highly plausible).
There will be too many bug reports to handle, Launchpad changes are required for this to work.
1st step:
After spotting the typo the users can just click on Help -> Report a broken translation.
This action will launch a series of actions starting with gnome-screenshot -a (that will capture a specific area of the screen) the next actions should somehow prepare the file and add save it to a temp folder (/tmp in our case, gnome-screenshot).
2nd step:
The user will be presented with a crosshair so he can select the desired area, (small floating message on top to bottom of the screen is optional, we have to make sure that the screenshot tool will not capture the message ☺)
3rd step:
The user will have an option to state exactly what seems wrong in his opinion and offer a correction. (in 2 distinct text boxes, 3rd box for comments is optional and I didn't add that in the mockup)
Another option we can offer (does not appear in the mockup) is to add a small window on top that will show the user a thumbnail of the captured area.
4th step:
The following screen associates the typo report to the user using 3 options:
The user will have the ability to log into his Launchpad account.
The user does not have a Launchpad account and he decides this is the right time to sign up.
The user have no interest in a Launchpad account, but he wishes to be informed of any further progress.
The first option will show a username/password boxes for logging in.
The second option will open the default browser with a registration pag, the two option are: sending the report at this step and not publishing it until the user sign up, if the user does not sign up the report is deleted within 24 hrs, the second option is adding a message at the end of the registration progress, at this point the user will dismiss the browser window and go back to the report window where he can sign in and continue.
The third option will show a text box for entering an email address and a captcha (turing test) and a checkbox so the user will have the option to subscribe, we should consider whether its safe to let the users submit reports anonymously.
This step involves the usage of apport (which I'm not familiar with), apport will collect the needed info about the system language etc. including the app name and version and will make sure that the report is good enough, apport also has the option of adding files to Lunchpad bug reports, this makes reporting a little more automatic (future thoughts: make this a GNOME native function using bug-buddy).
5th step:
The final screen, which shows a short greeting (your bug report has been submitted or otherwise not submitted in case there was an error and maybe even tells you what went wrong).
The link to the bug in the middle.
And finally a short message that thanks the user for taking the time to make the open source better.