Flagging GeoIP project as being ineligible for GSoC
Damian Johnson commited on 2012-03-01 17:59:11
Zeige 1 geänderte Dateien mit 4 Einfügungen und 4 Löschungen.
We previously had a note saying that this was a no-go for GSoC but it had been commented out. If this was git then I'd use 'git blame' to figure out why, but not worth the effort to try to get this information from svn. Suggested revision by Robert Ransom.
- getinvolved/en/volunteer.wml aed8bf800..6a016e2ad
| ... | ... |
@@ -953,18 +953,18 @@ meetings around the world.</li> |
| 953 | 953 |
Skill Level: <i>Medium to High</i> |
| 954 | 954 |
<br> |
| 955 | 955 |
Likely Mentors: <i>Robert Ransom</i> |
| 956 |
- <p>Currently, Tor bridges and relays read an entire IP->country database |
|
| 956 |
+ <p>Currently, Tor bridges and relays read an entire IP->country database |
|
| 957 | 957 |
into memory from a text file during startup. We would like to |
| 958 | 958 |
distribute this database and store it on disk in a much more compact |
| 959 |
- form, and perform IP->country lookups on it in its on-disk format if |
|
| 959 |
+ form, and perform IP->country lookups on it in its on-disk format if |
|
| 960 | 960 |
possible.</p> |
| 961 | 961 |
<p>We have <a href='https://trac.torproject.org/projects/tor/ticket/2506'>a |
| 962 | 962 |
sketch of a design</a> for a moderately optimized format for IPv4 GeoIP |
| 963 | 963 |
data; this project will involve both implementing the IPv4 format and |
| 964 | 964 |
designing and implementing a format for IPv6 GeoIP data.</p> |
| 965 |
- <!--<p>Since the core of this project is researching IPv6 GeoIP data and |
|
| 965 |
+ <p>Since the core of this project is researching IPv6 GeoIP data and |
|
| 966 | 966 |
designing the IPv6 format, this is not likely to be a good GSoC |
| 967 |
- project.</p>--> |
|
| 967 |
+ project.</p> |
|
| 968 | 968 |
</li> |
| 969 | 969 |
|
| 970 | 970 |
<!-- |
| 971 | 971 |