- 论坛徽章:
- 0
|
Google code FAQ
Frequently Asked Questions
About Google Code
What is code.google.com?
Who are the people behind code.google.com?
Google's Open Source Projects
Which projects are being released?
Why did you choose these particular projects?
Are these programs still in active use at Google?
Who is their intended audience?
Why are you releasing code through Sourceforge?
What licenses are the projects provided under?
How are licenses chosen at Google?
What will you release next?
How can I communicate with other developers on a particular project?
Google APIs, File Formats, and other Hackery
What APIs, file format information and feeds does Google offer for external developers who wish to code solutions that use Google services?
Other Questions
What if I have questions about code.google.com?
What xml feeds are offered from code.google.com?
What is the featured project on the main page all about?
In what other ways does Google share its knowledge with external developers?
Google Summer of Code questions are answered in seperate FAQs for students and mentors.
About Google Code
What is code.google.com?
Code.google.com is our site for external developers interested in Google-related development. It’s where we’ll publish free source code and lists of our API services.
Who are the people behind code.google.com?
A lot of people worked together to both prepare source code for release and prepare code.google.com for launch and ongoing maintenance. We really care about free and open source software (F/OSS) at Google, and this site is one aspect of that affection.
Google's Open Source Projects
Which projects are being released?
We've chosen 4 projects to start out. Perftools, sparsehashtable, coredumper and goopy/functional. Details can be found at http://code.google.com/projects.html
Why did you choose these particular projects?
Well, several reasons, actually.
Google Engineers picked them.
You may have heard about 20% time, in which Google engineers are encouraged to work on a personal project one day out of the week. Open Source interests a lot of Google developers, so we thought taking advantage of this program was a good way to prepare code for release and maintenance.
They make future releases possible.
The programs we've chosen are all what we consider infrastructural programs. By releasing these tools, we will be able to release more software that relies on them later.
These are the ones that were ready first.
Are these programs still in active use at Google?
They aren't just in active use; they're in active development. These first projects are all current, actively maintained code straight out of our repositories, and as we improve them, those improvements will be merged into the free code base.
Who is their intended audience?
The code we're initially releasing is targeted at professional software development engineers who work with multi-threaded templated C++ code or who want functional features in python. We know that this is a somewhat limited audience; we made this decision specifically so we can work with a smaller community to iron out any bugs in our release and ongoing maintenance processes. Over time, we plan to release more tools useful to broader groups of developers.
Why are you releasing code through Sourceforge?
Well, because they were nice enough to oblige, and because developers here like Sourceforge. Future homes for new projects might include Tigris.org or language specific sites like the Vaults of Parnassus and CPAN.
What licenses are the projects provided under?
The first set are being released under the BSD 2.0 new license, to encourage their use in all kinds of software projects.
How are licenses chosen at Google?
We generally default to the preference of the open source release engineer who dedicates their time to releasing the code. Most of those currently involved are comfortable with the BSD license for these infrastructural developer tools. Future projects are as likely to be released under the Apache, MIT or GPL licenses.
What will you release next?
We've got a long list of software we want to release, so consider subscribing to our updates feed or discussion list, for more news as it happens.
How can I communicate with other developers on a particular project?
We've set up a discussion list for each project on Google Groups, which is monitored by other external developers on the projects and the Google engineer whose 20% time made the code release possible. Google's Open Source program manager, Chris DiBona, also monitors the lists to ensure that we keep doing a good job of interacting with outside developers.
Google APIs, File Formats and other Hackery
What APIs, file format information and feeds does Google offer for external developers who wish to code solutions that use Google services?
Please see our APIs page on this site for pointers to all official APIs, feeds and file formats.
Other Questions
What if I have questions about code.google.com?
We encourage you to visit the code.google.com community on Google Groups. Here, developers share their Google Code questions and expertise. You're also welcome to email us at code@google.com; however, since Google Code is in such early stages of development, we're focusing our energy on developing this site. Although we're unable to send personal responses to every email we receive, we do read all of the feedback that's submitted and will use it to improve Google Code.
What XML feeds are offered from code.google.com?
We've set up two main XML feeds: updates and featured projects. The featured project will update weekly at a minimum and updates will update more often.
What is the featured project on the main page all about?
These are projects that use a Google API or have used code we've released in a way that we think is cool. If you'd like to submit a project that you think should considered, please email code@google.com and let us know.
In what other ways does Google share its knowledge with external developers?
Googlers publish papers online and in scientific journals and present all over the world. If you would like to invite a Googler to speak at your event, please contact our public relations department at press@google.com. We can't satisfy every request, but we'd love to know about your event even if we can't attend. |
|
免费注册
楼主: prolj
发表于 2006-07-29 17:33
发表于 2006-07-31 16:05
