![]() |
|
|
|
|
|
||||||||||
|
| User list | You are not logged in.
Hey all,
I'm writing this on the behalf of Autopano Pro team. We will be doing doing a bit of restructuring of the Forums in the coming days. Here's what changes:
1. Support forum will become Using Autopano. It will not accept any bug reports, stability issues, crash reports, etc. It will be dedicated to using APP only. Such topics are usually by users, who seek a better way to solve a specific panorama case, or just looking for basic instructions.
2. Development forum is now Bug Reports. It will gather all bug reports, regarding any software version - latest beta, stable, Linux, Mac, PC - everything. This forum will be moderated in a bit different fashion from now on. Each topic title must begin with a APP version and platform. For example: [RC4, PC] Program Crash - unknown reason
Also, no more super-topics, Panorama Fanatic's style. Each bug MUST HAVE its own topic. This is the way Alexandre wants it and it's much closer to his own workflow.
After a problem is reported, Alexandre will review the topic and comment on it - whether it is a confirmed bug, not a bug, request for clarification, etc. Then, I'll put a resume of the bug online, on a Wiki page, which will serve as an global bug list. Solved bugs will be marked by Alexandre in the Wiki; I will reflect the status on the forum topic - close and move in the Archives forum. Which brings me to:
3. A new Archives forum, which will become a repository of resolved problem topics, bug reports that are not really bugs, topics from the Using APP forum that are asked frequently and contain only reference to other topics and other stuff that we don't want to clutter the forums, but we need to keep for future reference.
By the way, the new bug reporting and solving workflow will have two side effects:
- You can monitor which bugs are fixed and the general progress of APP via RSS subscription to the Recent Changes page
- The contents of the bugs page in the Wiki will become a base for the version history of APP
That's all for now, we'll keep you posted on the development of v1.3.1!
-------
1. Le forum 'Support en français' va devenir "Utilisation d'Autopano". il n'acceptera pas les posts sur les bugs, les posts sur la stabilité de l'application, les logs de crash, etc. Ce forum est dédié uniquement à l'utilisation d'APP, pour les utilisateurs qui recherchent ou proposent des trucs et astuces sur l'utilisation du logiciel, par exemple pour résoudre certains cas difficiles de panoramas, ou tout simplement se renseigner ou poser des questions sur certaines fonctionnalités du programme.
2. Le forum "Version beta" devient maintenant le forum "Bugs dans APP", qui rassemblera l'ensemble des posts sur les bugs de l'application, et ce, quelques soient les versions (Beta, RC, Stable) et les plateformes (PC, MAC, Linux). Bref, tout ce qui concerne les méchantes bestioles qui se cachent partout. Ce forum sera géré d'une manière stricte : Chaque titre de post devra commencer avec le numéro de version d'APP et la plateforme concerné. Par exemple : [1.3 RC4, PC] Crash du Programme Crash - Raison inconnu
Ainsi, plus de super-posts du style de Panorama Fanatic. Chaque bug DOIT AVOIR SON PROPRE POST. C'est ce que souhaite Alexandre, car cela facilitera le traitement et la résolution de chaque bug.
Après qu'un bug soit soulevé dans ce forum, Alexandre fera un commentaire dans le post concerné, que le post fasse référence à un bug réel ou non. Après, un résumé du bug sera mis dans le wiki, qui servira comme liste de référence des bugs tracés. Les bugs corrigés seront flagués par Alexandre dans le wiki, le post concerné sera fermé et déplacé dans le forum "Archive", ce qui nous amène au troisième forum :
3. Le forum "Archives" contiendra tous les anciens posts sur les problèmes résolus dans APP. Ce forum permettra aussi d'archiver les posts en doublon, les posts sur des questions X fois posées, ou tout simplement les posts sur des pb/bugs qui n'en sont pas réellement. Bref, tout ce qui peut poluer inutilement les autres forums, mais dont on veut quand même garder une trace.
Offline
I did the patch for subforums ... I hope I didn't break anything. If anyone can see a weird behavior of the forum, just send me an email ![]()
---
So the good news : we can have subforums now. This will allow to move around topics : for example when bugs are solved and confirmed solved => archives.
*
Offline
Could any of you suggest proper names and descriptions for the French couterparts of the new/renamed forums, so I can change them? Thanks!
Offline
Je propose les choix suivants pour le forum francais (à valider par Alexandre) :
1. Support forum will become Using Autopano.
"Utilisation d'Autopano"
2. Development forum is now Bug Reports.
"Bugs dans APP"
ou "Liste des bugs en cours"
ou "Bugs"
ou "Bug Reports" qui finalement va très bien, même en francais
Offline
Hey Taf, thanks for the translation! I moved it in the first post - more appropriate. Sorry to be a pain in the @$$, but could you do those too:
Share your tips and tricks here or get help with any Autopano Pro problem! No bug reports (of any kind) in this forum!
Found a bug in Autopano Pro? Let the developers know by submitting it in this forum.Please read the posting rules before starting a topic!
Got some great idea or a feature request? Post it here and discuss it. The most requested concepts are usually implemented, as Autopano Pro is very community driven.
Thanks!
Offline
Here is the translation :
Partagez vos trucs et astuces dans ce forum ou obtenez de l'aide sur l'utilisation d'Autopano PRO. ATTENTION, pas de post sur les bugs, il y a un autre forum dédié pour cela...
Vous avez trouvez un bug dans Autopano PRO ? Faites le connaitre à l'équipe de développement en créant un post dans ce forum. Merci de lire les rêgles de publication avant de créer votre post.
Vous avez de nouvelles idées, ou une proposition d'évolution pour Autopano Pro ? Lachez vous dans ce forum... toute idée est bonne à prendre. Autopano est une communauté active ou vous êtes invité à participer, et les bonnes idées sont souvent incorporées aux futures versions du logiciel.
----------------------------
Voilà, j'avoue avoir eu un peu de mal a traduire certaines tournures (surtout la dernière phrase... que je trouve maladroite dans ma traduction), mais j'espère avoir été dans l'esprit initial. Si il y a d'autres propositions, ne pas hésiter à me corriger.
Offline
Thanks for the translation! Updated...
Offline
TAF wrote:
Si il y a d'autres propositions, ne pas hésiter
Before you answered, I was tempted to translate those sentences but, no, I found it was too difficult. News papers headlines look nearly impossible to translate from English...
Voici ma tentative, juste pour le plaisir d'essayer:
Offline
Erm, I don't understand French, could you tell me which to use?
Offline
I vote GURL
Offline
Je pense que GURL à l'art de faire passer le même message en 2x moins de mots ![]()
---
Sorry [bo], here's the translation : I think GURL has the skill for telling the same thing in 2x less words.
Offline
Oh come on
You could've written that in English
The Babelfish is not really helpful! I'm leaving this French business in the hand of the French then. Alex can put the ones he want.
Offline
Hi,
I just noticed that this page is total outdated: http://www.autopano.net/wiki-en/Current_development
Is there something similiar with the current development infos?
Or is there an open bug tracker? Would like to get some more insight into to trouble ticket numbers you always post ... because "0001132: [Cortex ( rendu )] Render crash issue – resolved" doesn't tell me excactly which bug has been resolved ... ;-)
and / or is there a detailed changelog for APG?
Thx
Andreas
Offline
I'd think not. This was replaced in part by the blog/announcement forum.
Offline
It would help if we gain read access to the bugtracker - so we can see what bugs are known / whats the status and what bug/fix/ehancement is referred to in the announcement ;-)
Offline
It probably will and it has been requested by users many times! But in the end it's for the developers to decide. (And it also is a foot in the door - now you want read access for some users, after that for all users, then write access for some...
)
Offline
well - write open ticket systems proved good for many projects! ;-)
bugs are created direct in the ticket system, duplicated reports of bugs are reduced, increased information flow, ..., ... lot's of benefits - but I don't want to go that far ... read access would be enough ;-)
Maybe you could suggest it to the devs?
Offline
We'll talk about that in next monday briefing.
Offline
Powered by PunBB
© Copyright 2002–2005 Rickard Andersson
|
CHOOSING KOLOR Why choose Kolor? Which solution to choose? Download a trial Where can I buy? Education |
SOFTWARE Autopano Pro Autopano Giga Panotour Panotour Pro XnView |
ACCESSORIES Training DVD Panobook PROJECTS Paris 26 Gigapixels Yosemite 17 Gigapixels |
COMMUNITY Forums Blog |
COMPANY About Kolor Corporate blog Resellers Contact |
PRESS Press center Press review TOOLS My account |
