1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] maint db, rails and hosting
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20maint%20db%2C%20rails%20and%20hosting&In-Reply-To=%3CAANLkTimjy9W%3DaCjOe2TBKVOta_x_PbrJFB-QevQaSoXy%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001651.html">
<LINK REL="Next" HREF="001518.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] maint db, rails and hosting</H1>
<B>Romain d'Alverny</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20maint%20db%2C%20rails%20and%20hosting&In-Reply-To=%3CAANLkTimjy9W%3DaCjOe2TBKVOta_x_PbrJFB-QevQaSoXy%40mail.gmail.com%3E"
TITLE="[Mageia-sysadm] maint db, rails and hosting">rdalverny at gmail.com
</A><BR>
<I>Wed Jan 5 17:38:24 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="001651.html">[Mageia-sysadm] [212] - merge trunk ( for good this time )
</A></li>
<LI>Next message: <A HREF="001518.html">[Mageia-sysadm] maint db, rails and hosting
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1516">[ date ]</a>
<a href="thread.html#1516">[ thread ]</a>
<a href="subject.html#1516">[ subject ]</a>
<a href="author.html#1516">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hi there,
After we noticed that the existing maintainer-db app had no license,
we ought to reimplement it, fast.
I asked about this on the webteam list with some requirements and
kosmas kindly took the hold for this, proposing to implement it with
Rails [1]. As I stated in the original call (and later confirmed [2])
Rails was a possibility (as well as Django), forgot to mention
Symphony (was pointed out later); goal was to: stay open to new
contributions and try, if it came, with some technology that is easy
enough to host and still a bit new in this community.
As misc noticed me, yes, I didn't ask sysadm first about this (hosting
st else than PHP/Perl stuff); I have to admit that I expected the
point to be raised on the webteam ml at the time (the whole
conversation started in a meeting point pre-summary and took over 6
days before I said go).
So, yes, that means we would be to host a Rails app; it's not for the
sake of trying any type of buzz'd-about technology out there, it could
have been Django as well or Symphony. I didn't suggest erlang,
node.js, go or tcl frameworks. :-p
As a sidenote, kosmas set his own repository over gitorious.org but
has been notified that the master branch should move to mageia.org
infra at least when stable and in anyway, as soon as a repository is
set up for it. Same for issues (as soon as Bugzilla is up,
bugs/requests will move there, if there were any already before).
So, this mail was about clarifying the point; I'll try better next
time. As for hosting the thing, I asked kosmas about the requirements;
given the app needs, it will be a basic Rails/MySQL setup I guess, but
better wait for his take and his help.
What's your take on this?
- hosting Rails apps; how/where to host them (remember we have Gandi vhosts);
- how we can deal with open contributions, specifying base
requirements for the tools we expect to receive (being square, but
flexible enough to accept more contributions); and what these
requirements would be;
- how it's acceptable that people use infrastructure outside of
mageia.org to bootstrap their contributions (like, still pointing that
a master branch should be reasonably migrated to mageia.org infra, or
other guideline);
- how we can better advertise our infrastructure and services (how
they work, how they can be used) *wink* and the sysadm team needs
(more contributions/contributors)
Cheers,
--
Romain
[1] <A HREF="https://mageia.org/pipermail/mageia-webteam/2010-December/000064.html">https://mageia.org/pipermail/mageia-webteam/2010-December/000064.html</A>
[2] <A HREF="https://mageia.org/pipermail/mageia-webteam/2010-December/000070.html">https://mageia.org/pipermail/mageia-webteam/2010-December/000070.html</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001651.html">[Mageia-sysadm] [212] - merge trunk ( for good this time )
</A></li>
<LI>Next message: <A HREF="001518.html">[Mageia-sysadm] maint db, rails and hosting
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1516">[ date ]</a>
<a href="thread.html#1516">[ thread ]</a>
<a href="subject.html#1516">[ subject ]</a>
<a href="author.html#1516">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>
|
