Back when we only had a mailing list, we really needed a separate issue tracker because issues tracking doesn’t work on mailing lists. The issue tracker we have now is great because it’s connected with the code and easy to work with. And we get less problem reports on the mailing list, which is good, because the mailing list is not suited for problem reports. Old threads get lost and people wonder why their problem is not attended to.
Back when we didn’t have a forum the mailing list was swamped with users asking the same questions over and over again. Now that we have the forum there is a point of reference and users helping users. Code issues bubble up and are referred to us by Mark. There is a reason why we have all three platforms. The single point of contact is http://owncloud.org On Thu, Mar 21, 2013 at 4:53 PM, Thomas Gries <[email protected]> wrote: > Am 21.03.2013 16:43, schrieb Thomas Tanghus: > > ...Please don't use the isue tracker for asking > > questions about how to do what, unless it's clearly a usability issue > which > > should be solved. Use http://forum.owncloud.org/ for that - > -1 > > This is clearly "divide et impera" > > - mailing list > - forum > - github issue tracker > > You should have *one* single point of contact. > > > > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud >
_______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
