well, strictly speaking, being indexed by google is not synonym to being public. (and, of course, that don't means we don't miss or want it)
On 8 August 2013 18:10, Esteban Lorenzano <[email protected]> wrote: > that's a restriction made by the service we choose. > issues are publicly visible here: > > http://bugs.pharo.org > > and there you also can register your self so you can also edit issues in > fogbugz. > so yes... is public in the "non-restricted access" meaning of the word. > > Esteban > > On Aug 8, 2013, at 4:57 PM, Mark Bestley <news{@bestley.co.uk> wrote: > >> Igor Stasenko <[email protected]> wrote: >> >>> On 8 August 2013 13:35, Levente Uzonyi >> <[email protected]> wrote: > > On Thu, 8 Aug 2013, >> Stéphane Ducasse wrote: > > g the issue on a public tracker means >> private? > > > > > > How is that a "public tracker"? > > > > can you >> elaborate? > https://pharo.fogbugz.com/ > is publicly accessible, no? or >> what makes you think it is not public? > >> >> Take the first bug fix from the Pharo Summer release details at >> <https://pharo.fogbugz.com/f/cases/10014/World-menu-System-Switch-User-s >> erves-no-purpose> >> >> This gives a the fogbugz log in page so to get info you need to login so >> not public (also are the bugs indexed by google?) >> >> >> -- >> Mark >> >> > > -- Best regards, Igor Stasenko.
