On Sun, Feb 14, 2016 at 11:03 AM, sebb <seb...@gmail.com> wrote: > The people public data currently only includes id, name, and noLogin > (disabled login) status. > > This is adequate for most purposes, however there are use cases for > additional info. > > For example, reporter.a.o needs the creation date (to show committer > number changes) > > One could add the information to the existing data file, but this > would increase the file size. > This would increase resource usage unnecessarily for most cases. > > I'm therefore thinking it would be useful to provide a second version > with more info. > This could be generated by the same cronjob - it would just create an > additional file.
Just a guess, but reporter.apache.org only needs to know the dates for people who have been added in the last 90 or so days? > The alternative is for apps to continue to use LDAP directly for such info. How is that a problem? > Thoughts? Generally, I'm opposed to premature optimization. And to building something that a tool might need. If the reporter tool is run a few dozen times a month, and is only looking at three months of data, extracting a complete list of every person and their creation date every 15 minutes seems like overkill. A cgi script that returns on demand a more customized result might be a better fit. - Sam Ruby
