Done. I also updated the section about Mustella.
EdB
On Mon, Oct 8, 2012 at 3:02 PM, Carol Frampton wrote:
> Not directly related to this conversation but related to the Apache Flex
> website.
>
> Would it be possible for someone to update the "Getting the source code"
> section in [1]?
>
> It
Not directly related to this conversation but related to the Apache Flex
website.
Would it be possible for someone to update the "Getting the source code"
section in [1]?
It should mention that active development on the sdk is being done in
branches/develop and we release from trunk.
We might al
There is no need for a service to help with the HTML etc., Ashish
Desai and the guys at Zootar already did a marvelous job with that.
They did an excellent job of bringing Fuse Collective design to life.
Take a look at:
http://www.zootar.com/apache/
This is what I'm now working on bringing to th
Hi everyone,
I think using htmlburger is not good idea because of:
- price (first page + a few second pages)
- we don't have due date (so we can do it when we have time)
- there are mature html/css developers in community.
(let me know if I'm wrong)
P.S. I have a little free time on weekends, so
I'm already working on this. The development corner is at:
http://flex.staging.apache.org/flex/again/
I added most code just yesterday, as it took some digging into obscure
documentation to figure out how to tame the CMS to allow for the
requirements of the design.
I will be adding the nice thin
A PSD is all we would need to pass off to htmlburger, if the community is
ok with that I have no problem taking care of it.
On Sat, Oct 6, 2012 at 4:09 PM, Nicholas Kwiatkowski wrote:
> We do have a PSD, but there hasn't been much progress past that. I,
> personally have also been slammed at wor
We do have a PSD, but there hasn't been much progress past that. I,
personally have also been slammed at work and my other commitments.
Hopefully things should ease up in a few weeks, but until then...
-Nick
On Sat, Oct 6, 2012 at 1:53 PM, Francis Altomare wrote:
> Hi Everyone,
>
> I was just
Sounds like a plan. Let me know your findings. I will also go through the CMS
link you have shared to understand how we can design the site to fit snugly
with CMS.
Lets start page by page. Let's see how much re-design it takes to get the
index.html redrafted to work with CMS. We can then make t
Ashish,
> Please see my comments inline. A also very easy route would be somebody
> voting me in as a committer. Don't like to ask it out, but I think I have
> dedicated considerable time and my resources to the cause.
I sympathise and agree. Not very long ago I was in exactly your
position. Pa
HI,
> So, you're free to work in Git, or whereever, but we need to figure
> out how we're going to get the changes you make to me (or any other
> committer) and how you are going to implement the changes I need to
> make it work in the CMS on your end.
There is a GIt mirror of the site here:
git:
Please see my comments inline. A also very easy route would be somebody voting
me in as a committer. Don't like to ask it out, but I think I have dedicated
considerable time and my resources to the cause.
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Sep 16, 2012, at 6:06 PM, Erik de Bru
I'm not seeing how that would work. For the code to work in the CMS,
we need to create one or more templates. The content will then have to
be adopted to work in those templates. For a reference and examples,
please see:
http://www.apache.org/dev/cmsref
Now, the example sites shown on that page
Understood, so let's follow this procedure:
1. We will push all our changes to GitHub.
2. We will notify this list about our activity on GitHub repo.
3. You guys can then pick up those files, have a review and let us know what
needs to change for your CMS integration.
4. Since my guys understand t
Ashish,
I'm not sure we understand each other. In order to integrate with the
CMS, I'll have to make substantial changes to the code you submitted
in the JIRA ticket. This means that I'll be effectively be working on
a branch of your code. This branch can only work IN THE CMS. So future
changes yo
I was not able to upload to the repository Om created. Not sure why, but i
created a new repository and will upload the code over there soon.
https://github.com/asdesai/ApacheFlexWebsite.git
The only way for multiple persons to work on this is to use source control.
Since majority of the develop
I'm looking at the code right now, thanks for the upload. And with
modifications I'm sure I can get a pretty close approximation working
in the CMS.
I was confused by all the talk about Git and Github. Maybe I missed
something. What are you trying to achieve using those tools?
EdB
On Sun, Sep
I am confused:-(. What issue are we trying to address here? Committing the code
or integrating the code with CMS?
Once again, the code is already uploaded to the JIRA ticket.
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Sep 16, 2012, at 5:09 PM, Erik de Bruin wrote:
> Hi,
>
> Since
Hi,
Since this project will be heavily dependant on the custom Apache.org
CMS, I don't see how we can collaborate other then using the site's
SVN repo and patches on JIRA tickets (for the non-committers). Please
correct me if I'm wrong.
EdB
On Sun, Sep 16, 2012 at 9:35 PM, Om wrote:
> Done.
>
The code is already attached to the JIRA ticket. I will take some time to get
it checked in into GitHub. Could we use the full codebase attached to the JIRA
ticket meanwhile?
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Sep 16, 2012, at 3:35 PM, Om wrote:
> Done.
>
> But, since Nick
Done.
But, since Nick and Erik (both committers) are involved, we can probably
get the first version committed and you could continue contributing as
patches. That way anyone else who wants to contribute can do so as well
off of SVN.
Thanks,
Om
On Sun, Sep 16, 2012 at 11:28 AM, Ashish Desai - Z
Om,
Here is my git hub user id, can you please grant access to the repository?
user: asdesai
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Aug 2, 2012, at 4:10 PM, Ashish Desai wrote:
> Thanks om this helps. I will give you my user details soon.
>
> Om wrote:
>
>> Ashish,
>>
>> I hav
Thanks om this helps. I will give you my user details soon.
Om wrote:
>Ashish,
>
>I have created a new repo here:
>https://github.com/bigosmallm/ApacheFlexWebsite
>
>You will need to create an account on github.com and give me your userid so
>I can add you as a collaborator to this Repo. Anyon
Ashish,
I have created a new repo here:
https://github.com/bigosmallm/ApacheFlexWebsite
You will need to create an account on github.com and give me your userid so
I can add you as a collaborator to this Repo. Anyone else interested in
helping out, please do the same and I can add you as collab
Om,
Could you setup the github project for the new website and also give me some
pointers on how to integrate with CMS? I think we can do the work of
integrating with CMS for Nick.
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Jul 5, 2012, at 4:22 PM, Om wrote:
> Not a problem, Ashish
Not a problem, Ashish. As I said, no pressure :-)
I will set up a public github project and send the instructions soon.
Thanks,
Om
On Thu, Jul 5, 2012 at 12:55 PM, Desai, Ashish S <
ashish.s.de...@jpmorgan.com> wrote:
> Om,
> Give my team few days to build and join as many dots possible and pu
Om,
Give my team few days to build and join as many dots possible and put a version
that everyone can work upon. Does that sound reasonable?
Meanwhile, sure we can create a github project.
Thanks,
Ashish
-Original Message-
From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of
26 matches
Mail list logo
